reset_token_budget

Hard-reset all token budget counters. Destructive — prefer manual_token_cleanup.

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/reset-token-budget.md

WHAT IT DOES

What reset_token_budget does on Jshookmcp

AI agents call reset_token_budget 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 reset_token_budget is rated Critical

Irreversibly resets token budget counters without undo capability or recovery option.

From the tool's definition Hard-reset all token budget counters. Destructive.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs reset_token_budget 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 reset_token_budget, this is the rule to start with:

reset_token_budget Hidden

reset_token_budget 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": [
    "reset_token_budget"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about reset_token_budget

What does the reset_token_budget tool do? +

Hard-reset all token budget counters. Destructive — prefer manual_token_cleanup. 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 reset_token_budget? +

Register the Jshook MCP server in PolicyLayer and add a rule for reset_token_budget: 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 reset_token_budget? +

reset_token_budget 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 reset_token_budget? +

Yes. Add a rate_limit block to the reset_token_budget 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 reset_token_budget completely? +

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

reset_token_budget 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

team_manager_reset on Team Manager MCP →revoke_api_token on cPanel MCP Server →reset_mcp_runtime_metrics on 0xpdf → All critical-risk MCP tools → The MCP Attack Database →

Guides

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