Tool discovery
An agent sees only the MCP operations granted to its identity and delegation.
Developers · MCP gateway
Put policy between an agent and an MCP server.
Deixic accepts MCP over Streamable HTTP, limits the tools an agent can discover, and checks each call before an upstream credential is resolved.
Request path
The upstream tool does not run until policy decides.
- 01The agent connects with signed identity and delegation context.
- 02Deixic filters tool discovery to the operations allowed by its grants.
- 03A tool call is evaluated against policy before credential resolution.
- 04The call is allowed, denied, or held for a named approver.
- 05An approved call resumes against the upstream MCP server.
- 06The response is masked where policy requires and the decision and result are recorded.
Controls applied
Identity, capability, policy, and output stay on the same path.
Call decision
Policy can allow the call, deny it, or require approval before an upstream credential is used.
Held execution
A matching approval resumes the parked call; a denial leaves the upstream tool untouched.
Response handling
Recursive masking can remove protected response fields before the result returns to the agent.
Recorded after the call
Reconstruct which agent asked, what policy decided, and what ran.
Durable activity ties the tenant-bound decision to the tool call and its result. Development recordings can be written as JSONL while a gateway path is being tested.