script_set_code
A execute tool on the Mcp Anything MCP server.
This record as markdown: /tools/mcp-anything/script-set-code.md
What script_set_code does on Mcp Anything
AI agents invoke script_set_code to trigger actions in Mcp Anything. 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 script_set_code is rated High
A tool that sets script code is at minimum a Write operation (modifying code), but given the MCP-Anything context (a bridge to CLI and software automation tools), scripts set here are almost certainly intended to be executed. This makes it Execute or higher. The ability to set arbitrary code is critically dangerous if misused by an AI agent, as it could introduce malicious logic into scripts.
From the tool's definition Tool name 'script_set_code' implies setting/writing executable code. Empty description reduces certainty but the name strongly suggests modifying script content that can later be executed.
Attacks that exploit this kind of access
The rule that runs script_set_code safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For script_set_code, this is the rule to start with:
script_set_code 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 Anything, apply this rule, and every script_set_code call is checked against it from then on.
Questions about script_set_code
script_set_code is a execute tool on the Mcp Anything MCP server. It is categorised as a Execute tool in the Mcp Anything MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Anything MCP server in PolicyLayer and add a rule for script_set_code: 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 Anything. Nothing to install.
script_set_code 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 script_set_code 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 script_set_code. 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.
script_set_code is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Anything, and thousands of servers like it.
Across the catalogue