How to

How to use gatekeep

gatekeep gives every agent a real identity and checks policy before a tool call executes. Use this flow to move from access request to governed agent activity.

1

Request organization access

Submit the public access request with your organization name, your name, and a work email. A super admin reviews the request before creating the organization.

2

Accept the admin invite

After approval, the first admin receives an invite link. Set a password from that link, then sign in to the organization control plane.

3

Register the agents

Create identities for the agents that will call tools. Keep names, ownership, and scopes specific enough that an audit log can explain who acted.

4

Connect servers and tools

Add the MCP servers or tool gateways your agents need. Treat every connected tool as a security boundary with its own default policy.

5

Set policy decisions

Choose whether each tool should allow, require approval, or block calls by default. Use approval for sensitive actions that need human review.

6

Review approvals

When a risky call pauses, inspect the agent, tool, requested action, and context before allowing or denying the execution.

7

Watch activity and posture

Use activity and posture views to find stale grants, over-open tools, blocked calls, and agents that need tighter governance.

Decision modelEvery tool call resolves to allowed, approval required, or blocked.
Request access