Remove a tax action map entry from a fiscal position (l10n_bg_tax_admin).
AI agents call odoo_fp_remove_action 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.
The tool permanently deletes a tax action mapping entry, which cannot be undone and affects tax compliance configuration in Odoo. This is especially critical given the Bulgaria localization context (l10n_bg_tax_admin, НАП/tax authority integration), where incorrect or missing tax mappings could lead to non-compliance, incorrect tax reporting, or audit issues.
From the tool's definition Tool name contains 'remove' and description states it will 'Remove a tax action map entry from a fiscal position' — this is an irreversible deletion of fiscal configuration data.
Documented attack patterns abuse exactly the kind of access odoo_fp_remove_action gives an agent:
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 odoo_fp_remove_action:
{
"version": "1",
"default": "deny",
"hide": [
"odoo_fp_remove_action"
]
} odoo_fp_remove_action disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a tax action map entry from a fiscal position (l10n_bg_tax_admin). 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 odoo_fp_remove_action: 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.
odoo_fp_remove_action 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 odoo_fp_remove_action 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 odoo_fp_remove_action. 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.
odoo_fp_remove_action 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.
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.