AI agents call cf_tunnel_config to retrieve information from Access without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays Cloudflare Tunnel configuration data. The verbs 'Retrieve' and 'verify' clearly indicate a read-only operation. However, severity is elevated to 'high' because the configuration exposed reveals the internal network topology, hostname-to-service mappings, and tunnel architecture—information that could be weaponized by an attacker to identify attack surfaces, plan lateral movement, or…
From the tool's definition Retrieve the ingress routing configuration... showing which hostnames map to which local services. Use this to debug tunnel routing or verify configuration. The tool explicitly performs a retrieval/query operation with no modification capability.
Attacks that exploit this kind of access
Retrieve the ingress routing configuration for a specific Cloudflare Tunnel, showing which hostnames map to which local services. Use this to debug tunnel routing or verify configuration. It is categorised as a Read tool in the Access MCP Server, which means it retrieves data without modifying state.
Register the Access MCP server in PolicyLayer and add a rule for cf_tunnel_config: 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 Access. Nothing to install.
cf_tunnel_config 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 cf_tunnel_config 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 cf_tunnel_config. 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.
cf_tunnel_config is provided by the Access MCP server (scottpedia0/access). 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 →