set_request_header_rules_tool
AI agents use set_request_header_rules_tool to create or update resources in MCP Cloudflare — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Cloudflare environment.
The name suggests this tool sets (creates or modifies) request header rules on Cloudflare, which is a Write operation affecting HTTP request handling. This could have significant security implications (e.g., spoofing headers, bypassing security checks), hence high severity. However, confidence is reduced due to the empty description — it could also be Destructive if it overwrites existing rules entirely.
From the tool's definition Tool name: set_request_header_rules_tool; description is empty/uninformative.
Attacks that exploit this kind of access
set_request_header_rules_tool. It is categorised as a Write tool in the MCP Cloudflare MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Cloudflare MCP server in PolicyLayer and add a rule for set_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.
set_request_header_rules_tool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_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 set_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.
set_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 →