cf_tunnel_config_get

Get the current ingress/config of a tunnel.

SERVEROdoo Claude MCP SOURCErosenvladimirov/odoo-claude-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/cf-tunnel-config-get.md

WHAT IT DOES

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. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why cf_tunnel_config_get is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cf_tunnel_config_get safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Odoo Claude MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cf_tunnel_config_get, this is the rule to start with:

cf_tunnel_config_get Allowed

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cf_tunnel_config_get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every cf_tunnel_config_get call is checked against it from then on.

FAQ

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.

KEEP EXPLORING

More on Odoo Claude, and thousands of servers like it.

This server

All 246 Odoo Claude tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →