AI agents invoke calculator to trigger actions in MCP Reloader. 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.
A calculator tool runs computations based on user-supplied inputs. While typically benign, it falls under Execute since it processes and runs operations rather than purely reading static data. The description is very sparse ('Simple calculator operations'), which limits confidence.
From the tool's definition 'calculator operations' — the tool executes arithmetic/computation operations based on provided arguments
Documented attack patterns abuse exactly the kind of access calculator gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Reloader, and nothing reaches the server without passing your rules. This is the rule we recommend for calculator:
{
"version": "1",
"default": "deny",
"tools": {
"calculator": {
"limits": [
{
"counter": "calculator_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}calculator 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.
Free to start. No card required.
Simple calculator operations. It is categorised as a Execute tool in the MCP Reloader MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Reloader MCP server in PolicyLayer and add a rule for calculator: 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 Reloader. Nothing to install.
calculator 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 calculator 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 calculator. 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.
calculator is provided by the MCP Reloader MCP server (mizchi/mcp-reloader). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Reloader, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 MCP Reloader tools catalogued and risk-classified — across an index of 43,000+ MCP servers.