Low Risk

cf_tunnel_config_get

Get the current ingress/config of a tunnel.

How to control cf_tunnel_config_get ↓

What cf_tunnel_config_get does on Odoo Claude MCP

AI agents call cf_tunnel_config_get to retrieve information from Odoo Claude MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why cf_tunnel_config_get needs a policy

This is a read operation that queries tunnel configuration state. However, severity is medium rather than low because tunnel configuration details (ingress rules, routing paths, authentication tokens) could be sensitive information that might aid in lateral movement or reconnaissance if an AI agent exfiltrates it. The tool itself performs no side effects, but the data it exposes has moderate security implications.

From the tool's definition Tool name contains 'get' and description states 'Get the current ingress/config of a tunnel' — purely retrieves tunnel configuration data without modification.

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

How to control cf_tunnel_config_get

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_config_get:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cf_tunnel_config_get": {}
  }
}

cf_tunnel_config_get is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about cf_tunnel_config_get

What does the cf_tunnel_config_get tool do? +

Get the current ingress/config of a tunnel. It is categorised as a Read tool in the Odoo Claude MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cf_tunnel_config_get? +

Register the Odoo Claude MCP server in PolicyLayer and add a rule for cf_tunnel_config_get: 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_config_get? +

cf_tunnel_config_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cf_tunnel_config_get? +

Yes. Add a rate_limit block to the cf_tunnel_config_get 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_config_get completely? +

Set action: deny in the PolicyLayer policy for cf_tunnel_config_get. 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_config_get? +

cf_tunnel_config_get 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.