AI agents call listTodos to retrieve information from Cloudflare MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and displays existing todo items without creating, modifying, deleting, or executing any operations. It is a simple read query with minimal blast radius even if misused by an agent.
From the tool's definition Tool name is 'listTodos' and description states 'List all tasks in your todo list' — a pure retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access listTodos 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 listTodos:
{
"version": "1",
"default": "deny",
"tools": {
"listTodos": {}
}
} listTodos is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all tasks in your todo list. It is categorised as a Read tool in the Cloudflare MCP MCP Server, which means it retrieves data without modifying state.
Register the Cloudflare MCP server in PolicyLayer and add a rule for listTodos: 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.
listTodos is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listTodos 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 listTodos. 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.
listTodos 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.