List request header modification rules.
AI agents call list_request_header_rules_tool to retrieve information from MCP Cloudflare without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing request header modification rules without creating, modifying, or deleting any data. It is a straightforward read operation. The low severity reflects minimal blast radius—exposing an AI agent to this tool would only risk information disclosure about current rule configurations, not unauthorized changes or access to sensitive operations.
From the tool's definition Tool name contains 'list' and description states 'List request header modification rules' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List request header modification rules. It is categorised as a Read tool in the MCP Cloudflare MCP Server, which means it retrieves data without modifying state.
Register the MCP Cloudflare MCP server in PolicyLayer and add a rule for list_request_header_rules_tool: 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 Cloudflare. Nothing to install.
list_request_header_rules_tool 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 list_request_header_rules_tool 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 list_request_header_rules_tool. 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.
list_request_header_rules_tool is provided by the MCP Cloudflare MCP server (pypi:mcp-cloudflare-crunchtools). 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 →