toggle_dynamic_tool
Toggles the availability of the dynamic_feature tool
This record as markdown: /tools/mcp-test-servers/toggle-dynamic-tool.md
What toggle_dynamic_tool does on Mcp Test Servers
AI agents invoke toggle_dynamic_tool to trigger actions in Mcp Test Servers. 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 toggle_dynamic_tool is rated High
Toggling a tool's availability is an operational action that modifies the runtime state of the server. It is not a simple read, nor does it delete data or move money. It executes a configuration change that affects what capabilities are exposed to agents, which could be misused to enable dangerous tools or disable safety controls.
From the tool's definition 'Toggles the availability of the dynamic_feature tool' — enables or disables another tool's availability, triggering a state change in the server's tool registry
Attacks that exploit this kind of access
The rule that runs toggle_dynamic_tool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Test Servers, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For toggle_dynamic_tool, this is the rule to start with:
toggle_dynamic_tool 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Test Servers, apply this rule, and every toggle_dynamic_tool call is checked against it from then on.
Questions about toggle_dynamic_tool
Toggles the availability of the dynamic_feature tool. It is categorised as a Execute tool in the Mcp Test Servers MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Test Servers MCP server in PolicyLayer and add a rule for toggle_dynamic_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 Mcp Test Servers. Nothing to install.
toggle_dynamic_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the toggle_dynamic_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.
Set action: deny in the PolicyLayer policy for toggle_dynamic_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.
toggle_dynamic_tool is provided by the Mcp Test Servers MCP server (msfeldstein/mcp-test-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Test Servers, and thousands of servers like it.
Across the catalogue