AI agents invoke mul to trigger actions in Calculator MCP. 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.
The tool executes a multiplication computation. While it has no persistent side effects, it falls under Execute as it performs an active operation rather than merely retrieving existing data. The blast radius is extremely low since it only returns a numeric result with no system access.
From the tool's definition "Multiply two numbers" — performs a mathematical operation (execution of arithmetic logic) with no data storage or side effects
Documented attack patterns abuse exactly the kind of access mul gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Calculator MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for mul:
{
"version": "1",
"default": "deny",
"tools": {
"mul": {
"limits": [
{
"counter": "mul_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}mul 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.
Multiply two numbers. It is categorised as a Execute tool in the Calculator MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Calculator MCP server in PolicyLayer and add a rule for mul: 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.
mul 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 mul 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 mul. 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.
mul is provided by the Calculator MCP server (wrtnlabs/calculator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Calculator MCP, 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 Calculator MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.