run_code
AI agents invoke run_code to trigger actions in Zero Network MCP Server. 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.
run_code executes arbitrary code, which is an Execute-category action. Without a description, the scope is unclear, but code execution in a financial/payment context (suggested by server purpose) poses significant risk if misused by an agent—potential for unauthorized transactions, access to payment credentials, or logic manipulation.
From the tool's definition Tool name 'run_code' with empty description; context shows Zero Network MCP Server provides SDK integration and payment tools. The name 'run_code' indicates code execution capability.
Attacks that exploit this kind of access
run_code. It is categorised as a Execute tool in the Zero Network MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Zero Network MCP Server MCP server in PolicyLayer and add a rule for run_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 Zero Network MCP Server. Nothing to install.
run_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 run_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 run_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.
run_code is provided by the Zero Network MCP Server MCP server (zzero-net/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →