执行浮点数加法运算
AI agents use add to create or update resources in Calculator MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Calculator MCP environment.
An AI agent can call add faster than any human can review — one bad instruction and it creates or modifies resources in Calculator MCP by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
执行浮点数加法运算. It is categorised as a Write tool in the Calculator MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Calculator 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 Calculator MCP. Nothing to install.
add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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 Calculator MCP server (kelseyee/mcp_calculator). 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 →