manual_token_cleanup

Clear stale entries and reset counters to free 10-30% of token budget.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/manual-token-cleanup.md

WHAT IT DOES

What manual_token_cleanup does on Jshookmcp

AI agents call manual_token_cleanup to permanently remove resources in Jshookmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why manual_token_cleanup is rated Critical

Irreversibly clears entries and resets counters, potentially losing token tracking data.

From the tool's definition Clear stale entries and reset counters

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs manual_token_cleanup safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For manual_token_cleanup, this is the rule to start with:

manual_token_cleanup Hidden

manual_token_cleanup is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "manual_token_cleanup"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every manual_token_cleanup call is checked against it from then on.

FAQ

Questions about manual_token_cleanup

What does the manual_token_cleanup tool do? +

Clear stale entries and reset counters to free 10-30% of token budget. It is categorised as a Destructive tool in the Jshookmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on manual_token_cleanup? +

Register the Jshook MCP server in PolicyLayer and add a rule for manual_token_cleanup: 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 Jshookmcp. Nothing to install.

What risk level is manual_token_cleanup? +

manual_token_cleanup is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit manual_token_cleanup? +

Yes. Add a rate_limit block to the manual_token_cleanup 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.

How do I block manual_token_cleanup completely? +

Set action: deny in the PolicyLayer policy for manual_token_cleanup. 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.

What MCP server provides manual_token_cleanup? +

manual_token_cleanup is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools → Critical-risk tools on this server →

Across the catalogue

revoke_api_token on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →