Add two numbers
AI agents invoke add to trigger actions in Code Mode Bridge. 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.
While the tool itself ('Add two numbers') appears to be a simple arithmetic Read/Other operation, it exists within a sandbox execution environment that runs generated code. The server context elevates the risk category to Execute. However, the tool's own description is minimal and the arithmetic function itself has negligible blast radius, hence low severity and reduced confidence.
From the tool's definition Server description states it 'enables agents to run generated code in an isolated sandbox' and 'aggregates multiple upstream MCP tools into a single codemode tool for unified orchestration and execution'
Attacks that exploit this kind of access
Add two numbers. It is categorised as a Execute tool in the Code Mode Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Code Mode Bridge MCP server in PolicyLayer and add a rule for add: 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 Code Mode Bridge. Nothing to install.
add 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 add 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 add. 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.
add is provided by the Code Mode Bridge MCP server (ruifung/mcp-cm-bridge). 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 →