[OPERATOR] Revoke a delegation. Optionally cascade to all sub-delegations.
AI agents call revoke_delegation to permanently remove resources in Agent Passport System — Cryptographic Identity for AI Agents — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | Yes | Why the delegation is being revoked |
cascade | boolean | — | Also revoke all sub-delegations |
delegation_id | string | Yes | Delegation ID to revoke |
Parameters from the server's own tool schema.
Revoking a delegation removes granted permissions/authority, and cascading makes it affect all sub-delegations. These are irreversible trust-chain changes: once revoked, any dependent delegations and associated access rights are destroyed. This matches Destructive (irreversible removal), with high severity since misuse could strip legitimate agents of their authority across an entire delegation tree.
From the tool's definition 'Revoke a delegation. Optionally cascade to all sub-delegations.' — revocation is irreversible and cascading removes all downstream delegated authorities.
Documented attack patterns abuse exactly the kind of access revoke_delegation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Passport System — Cryptographic Identity for AI Agents, and nothing reaches the server without passing your rules. This is the rule we recommend for revoke_delegation:
{
"version": "1",
"default": "deny",
"hide": [
"revoke_delegation"
]
}revoke_delegation disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
All 150 Agent Passport System — Cryptographic Identity for AI Agents tools →
[OPERATOR] Revoke a delegation. Optionally cascade to all sub-delegations. It is categorised as a Destructive tool in the Agent Passport System — Cryptographic Identity for AI Agents MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
revoke_delegation accepts 3 parameters: reason, cascade, delegation_id. Required: reason, delegation_id. The full parameter table on this page comes from the server's own tool schema.
Register the Agent Passport System — Cryptographic Identity for AI Agents MCP server in PolicyLayer and add a rule for revoke_delegation: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Agent Passport System — Cryptographic Identity for AI Agents. Nothing to install.
revoke_delegation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the revoke_delegation rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for revoke_delegation. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
revoke_delegation is provided by the Agent Passport System — Cryptographic Identity for AI Agents MCP server (https://mcp.aeoess.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agent Passport System — Cryptographic Identity for AI Agents, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
150 Agent Passport System — Cryptographic Identity for AI Agents tools catalogued and risk-classified — across an index of 43,000+ MCP servers.