get_bgp_hijacks
Retrieve BGP hijack events. BGP hijacks occur when an AS announces routes it does not own, potentially redirecting traffic.
This record as markdown: /tools/cloudflare/get-bgp-hijacks.md
What get_bgp_hijacks does on Cloudflare
AI agents call get_bgp_hijacks to retrieve information from Cloudflare without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_bgp_hijacks is rated Low
This tool retrieves information about BGP hijack events—a read operation with no side effects. However, severity is elevated to medium because the data retrieved (BGP hijacks) relates to network security events that could inform an attacker about infrastructure vulnerabilities or misdirection opportunities if misused in conjunction with other tools on this Cloudflare server (such as container_exec or container_file…
From the tool's definition Tool name 'get_bgp_hijacks' and description 'Retrieve BGP hijack events' indicate a read-only query operation that retrieves historical or current BGP hijack data without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs get_bgp_hijacks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cloudflare, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_bgp_hijacks, this is the rule to start with:
get_bgp_hijacks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cloudflare, apply this rule, and every get_bgp_hijacks call is checked against it from then on.
Questions about get_bgp_hijacks
Retrieve BGP hijack events. BGP hijacks occur when an AS announces routes it does not own, potentially redirecting traffic. It is categorised as a Read tool in the Cloudflare MCP Server, which means it retrieves data without modifying state.
Register the Cloudflare MCP server in PolicyLayer and add a rule for get_bgp_hijacks: 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. Nothing to install.
get_bgp_hijacks 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 get_bgp_hijacks 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 get_bgp_hijacks. 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.
get_bgp_hijacks is provided by the Cloudflare MCP server (https://builds.mcp.cloudflare.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cloudflare, and thousands of servers like it.
This server
Across the catalogue