This record as markdown: /tools/1600822305-js-reverse-mcp/delete-token.md
What delete_token does on Js Reverse
AI agents call delete_token to permanently remove resources in Js Reverse, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_token is rated Critical
This tool permanently deletes stored tokens, which are typically authentication credentials or session identifiers. Deletion is irreversible and could prevent legitimate access to services or cause loss of authentication state. While not directly financial, the destructive nature of removing critical authentication artifacts warrants 'Destructive' classification.
From the tool's definition Tool name 'delete_token' combined with description 'Delete a saved token by name' explicitly performs an irreversible deletion operation. The action cannot be undone.
Attacks that exploit this kind of access
The rule that runs delete_token safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Js Reverse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_token, this is the rule to start with:
delete_token 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 Js Reverse, apply this rule, and every delete_token call is checked against it from then on.
Questions about delete_token
Delete a saved token by name. It is categorised as a Destructive tool in the Js Reverse MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Js Reverse MCP server in PolicyLayer and add a rule for delete_token: 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 Js Reverse. Nothing to install.
delete_token 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 delete_token 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 delete_token. 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.
delete_token is provided by the Js Reverse MCP server (1600822305/js-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Js Reverse, and thousands of servers like it.
Across the catalogue