Medium Risk

toggle_tool

Toggle a tool's enabled/disabled state

Part of the Try server.

toggle_tool can modify Try data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE TRY →

Free to start. No card required.

AI agents use toggle_tool to create or modify resources in Try. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call toggle_tool repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Try.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "toggle_tool": {
      "limits": [
        {
          "counter": "toggle_tool_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Try policy for all 13 tools.

Get this rule live on your own Try server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TRY →

View all 13 tools →

These attack patterns abuse exactly the kind of access toggle_tool gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so toggle_tool only ever does what you allow.

SECURE TRY →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the toggle_tool tool do? +

Toggle a tool's enabled/disabled state. It is categorised as a Write tool in the Try MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on toggle_tool? +

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

What risk level is toggle_tool? +

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

Can I rate-limit toggle_tool? +

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

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

toggle_tool is provided by the Try MCP server (https://install.md/mcp/try). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Try tool call.

Deterministic rules across all 13 Try tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.