Critical Risk →

cf_tunnel_route_remove

Remove ingress rule by hostname + delete its CNAME record.

How to control cf_tunnel_route_remove ↓

What cf_tunnel_route_remove does on Odoo Claude MCP

AI agents call cf_tunnel_route_remove to permanently remove resources in Odoo Claude MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why cf_tunnel_route_remove needs a policy

This tool permanently deletes network ingress rules and CNAME DNS records. These deletions cannot be undone without manual intervention and restoration procedures. The loss of DNS routing or network access rules could disrupt service availability.

From the tool's definition Tool description states 'Remove ingress rule by hostname + delete its CNAME record.' The verbs 'Remove' and 'delete' indicate irreversible deletion of network configuration and DNS records.

Documented attack patterns abuse exactly the kind of access cf_tunnel_route_remove gives an agent:

How to control cf_tunnel_route_remove

PolicyLayer is an MCP gateway — it sits between your AI agents and Odoo Claude MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for cf_tunnel_route_remove:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "cf_tunnel_route_remove"
  ]
}

cf_tunnel_route_remove disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Odoo Claude MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about cf_tunnel_route_remove

What does the cf_tunnel_route_remove tool do? +

Remove ingress rule by hostname + delete its CNAME record. It is categorised as a Destructive tool in the Odoo Claude MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on cf_tunnel_route_remove? +

Register the Odoo Claude MCP server in PolicyLayer and add a rule for cf_tunnel_route_remove: 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 Odoo Claude MCP. Nothing to install.

What risk level is cf_tunnel_route_remove? +

cf_tunnel_route_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cf_tunnel_route_remove? +

Yes. Add a rate_limit block to the cf_tunnel_route_remove 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.

How do I block cf_tunnel_route_remove completely? +

Set action: deny in the PolicyLayer policy for cf_tunnel_route_remove. 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.

What MCP server provides cf_tunnel_route_remove? +

cf_tunnel_route_remove is provided by the Odoo Claude MCP server (rosenvladimirov/odoo-claude-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Odoo Claude MCP tool call.

Start from Odoo Claude MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

180 Odoo Claude MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.