deactivate_tools

Remove previously activated tools to free context.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/deactivate-tools.md

WHAT IT DOES

What deactivate_tools does on Jshookmcp

AI agents use deactivate_tools to create or update resources in Jshookmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jshookmcp environment.

RISK

Why deactivate_tools is rated Medium

The tool modifies the state of the MCP server by removing/deactivating previously activated tools. This is a reversible configuration change (tools can presumably be re-activated), placing it in the Write category. Misuse could disrupt workflows by removing needed tools, giving it medium severity.

From the tool's definition Remove previously activated tools to free context

Attacks that exploit this kind of access

RECOMMENDED RULE

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

deactivate_tools Rate-limited

deactivate_tools stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deactivate_tools": {
      "limits": [
        {
          "counter": "deactivate_tools_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about deactivate_tools

What does the deactivate_tools tool do? +

Remove previously activated tools to free context. It is categorised as a Write tool in the Jshookmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on deactivate_tools? +

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

deactivate_tools is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit deactivate_tools? +

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

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

deactivate_tools 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 →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →