AI agents invoke add to trigger actions in Cloudflare 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.
This tool performs arithmetic computation. It has no side effects, no data modification, and no external operations. It could be classified as Read (pure query) or Execute (runs a computation). Given the sibling tool 'calculate' exists separately, 'add' appears to be a simple arithmetic operation. Severity is low as the blast radius of addition is negligible.
From the tool's definition "Simple addition of two numbers" — performs a calculation/computation
Documented attack patterns abuse exactly the kind of access add gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cloudflare MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for add:
{
"version": "1",
"default": "deny",
"tools": {
"add": {
"limits": [
{
"counter": "add_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}add 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 addition of two numbers. It is categorised as a Execute tool in the Cloudflare MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cloudflare 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 Cloudflare MCP. 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 Cloudflare MCP server (shashankboosi/cloudflare-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cloudflare 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.
7 Cloudflare MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.