This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/cf-dns-delete.md
What cf_dns_delete does on Odoo Claude MCP
AI agents call cf_dns_delete 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.
Why cf_dns_delete is rated Critical
DNS record deletion is a destructive operation that cannot be undone and has immediate blast radius—deleting records can take services offline, break email routing, or disable security configurations. This is more severe than Write (reversible modification) and qualifies as Destructive. High severity due to potential infrastructure impact.
From the tool's definition Tool name 'cf_dns_delete' and description 'Delete a DNS record' explicitly perform irreversible deletion of DNS infrastructure records.
Attacks that exploit this kind of access
The rule that runs cf_dns_delete 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_dns_delete, this is the rule to start with:
cf_dns_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every cf_dns_delete call is checked against it from then on.
Questions about cf_dns_delete
Delete a DNS 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.
Register the Odoo Claude MCP server in PolicyLayer and add a rule for cf_dns_delete: 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.
cf_dns_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cf_dns_delete 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_dns_delete. 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_dns_delete 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