This record as markdown: /tools/io-github-homenshum-nodebench/deeptrace-revoke-passport.md
What deeptrace_revoke_passport does on Nodebench
AI agents call deeptrace_revoke_passport to permanently remove resources in Nodebench, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why deeptrace_revoke_passport is rated Critical
Revoking an agent's passport is an irreversible action that permanently withdraws authorization or access credentials. This cannot be undone without explicit re-issuance and represents a destructive operation affecting system state. While not deleting data per se, it irreversibly terminates an agent's authentication/authorization, making it a destructive rather than merely write-level operation.
From the tool's definition Tool name contains 'revoke' which means to withdraw or cancel; description states 'Revoke an agent' indicating permanent removal or deactivation of an agent identity/credential.
Attacks that exploit this kind of access
The rule that runs deeptrace_revoke_passport safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deeptrace_revoke_passport, this is the rule to start with:
deeptrace_revoke_passport 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 Nodebench, apply this rule, and every deeptrace_revoke_passport call is checked against it from then on.
Questions about deeptrace_revoke_passport
Revoke an agent. It is categorised as a Destructive tool in the Nodebench MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nodebench MCP server in PolicyLayer and add a rule for deeptrace_revoke_passport: 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 Nodebench. Nothing to install.
deeptrace_revoke_passport 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 deeptrace_revoke_passport 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 deeptrace_revoke_passport. 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.
deeptrace_revoke_passport is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
Across the catalogue