get_bgp_routing_table_ases
List all ASes in global routing tables with routing statistics (prefix counts, IPv4/IPv6 address count, RPKI validation status). Data comes from public BGP MRT archives.
This record as markdown: /tools/cloudflare/get-bgp-routing-table-ases.md
What get_bgp_routing_table_ases does on Cloudflare
AI agents call get_bgp_routing_table_ases 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_routing_table_ases is rated Low
This tool queries and retrieves BGP routing information from public sources. It performs a read-only operation that retrieves network statistics and routing data without creating, modifying, deleting, or executing any operations. The data is sourced from public BGP archives, further confirming it is a passive data retrieval tool with no destructive or state-changing capabilities.
From the tool's definition Tool name contains 'get' and description states 'List all ASes' and 'Data comes from public BGP MRT archives' — indicates retrieval of publicly available routing data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_bgp_routing_table_ases 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_routing_table_ases, this is the rule to start with:
get_bgp_routing_table_ases 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_routing_table_ases call is checked against it from then on.
Questions about get_bgp_routing_table_ases
List all ASes in global routing tables with routing statistics (prefix counts, IPv4/IPv6 address count, RPKI validation status). Data comes from public BGP MRT archives. 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_routing_table_ases: 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_routing_table_ases 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_routing_table_ases 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_routing_table_ases. 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_routing_table_ases 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