New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

cf_tunnel_config_put

Replace the full ingress config. Last entry must be {'service': 'http_status:404'}.

SERVEROdoo Claude MCP SOURCErosenvladimirov/odoo-claude-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What cf_tunnel_config_put does on Odoo Claude MCP

AI agents use cf_tunnel_config_put to create or update resources in Odoo Claude MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Odoo Claude MCP environment.

Why cf_tunnel_config_put is rated Medium

This tool modifies (replaces) configuration data for ingress/tunneling, which is a reversible but impactful Write operation. The requirement that 'last entry must be {service: http_status:404}' suggests structural constraints to prevent misconfiguration.

From the tool's definition Tool name contains 'put' (HTTP verb for replacement); description states 'Replace the full ingress config', indicating modification of critical infrastructure configuration.

Questions about cf_tunnel_config_put

What does the cf_tunnel_config_put tool do? +

Replace the full ingress config. Last entry must be {'service': 'http_status:404'}. It is categorised as a Write tool in the Odoo Claude MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cf_tunnel_config_put? +

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

cf_tunnel_config_put is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cf_tunnel_config_put? +

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

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

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

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Odoo Claude's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.