signet_revoke
Revoke one of YOUR mandates by id. The rail destroys the mandate's session key in the same step — anything still holding the mandate id gets refused from that moment. This is the off switch you name when granting authority. Requires Authorization: Bearer <JWT>.
This record as markdown: /tools/ai-rokha-rokha/signet-revoke.md
What signet_revoke does on Rokha
AI agents call signet_revoke to permanently remove resources in Rokha, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
mandate_id | string | Yes | The mandate uuid (from signet_grant or signet_status) |
Parameters from the server's own tool schema.
Why signet_revoke is rated Critical
Irreversibly revokes authorization mandates and invalidates session keys, preventing further access permanently.
From the tool's definition Revoke mandates, destroys session key, off switch, anything holding mandate refused
Attacks that exploit this kind of access
The rule that runs signet_revoke safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For signet_revoke, this is the rule to start with:
signet_revoke is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every signet_revoke call is checked against it from then on.
Questions about signet_revoke
Revoke one of YOUR mandates by id. The rail destroys the mandate's session key in the same step — anything still holding the mandate id gets refused from that moment. This is the off switch you name when granting authority. Requires Authorization: Bearer <JWT>. It is categorised as a Destructive tool in the Rokha MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
signet_revoke accepts 1 parameter: mandate_id. Required: mandate_id. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for signet_revoke: 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 Rokha. Nothing to install.
signet_revoke 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 signet_revoke 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 signet_revoke. 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.
signet_revoke is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rokha, and thousands of servers like it.
Across the catalogue