dynamic.tool.enable · Dynamic MCP: Risk & Policy

WHAT IT DOES

What dynamic.tool.enable does on Dynamic

AI agents invoke dynamic.tool.enable to trigger actions in Dynamic. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why dynamic.tool.enable needs a policy

Enabling or disabling a dynamic tool at runtime alters system behavior and controls execution capabilities. This is not a simple read or write of data; it gates whether other tools (potentially code-executing or destructive ones) can be invoked. Misuse could expose dangerous capabilities or silently disable safety controls.

From the tool's definition 'Enable or disable a dynamic tool at runtime' — controls whether tools are active/inactive in the runtime environment

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dynamic.tool.enable Rate-limited

dynamic.tool.enable stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dynamic.tool.enable": {
      "limits": [
        {
          "counter": "dynamic.tool.enable_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Dynamic, so you can run agents against it safely.

FAQ

Questions about dynamic.tool.enable

What does the dynamic.tool.enable tool do? +

Enable or disable a dynamic tool at runtime. It is categorised as a Execute tool in the Dynamic MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on dynamic.tool.enable? +

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

What risk level is dynamic.tool.enable? +

dynamic.tool.enable is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit dynamic.tool.enable? +

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

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

dynamic.tool.enable is provided by the Dynamic MCP server (mcpland/dynamic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.