Add or update a tax action map entry for a fiscal position (l10n_bg_tax_admin).
AI agents use odoo_fp_configure 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.
The tool creates or modifies tax action mapping entries, which are configuration data that affect how Odoo processes tax obligations (НАП/ДДС compliance). This is reversible (can be undone by updating again), so it is Write rather than Destructive.
From the tool's definition Tool description states 'Add or update a tax action map entry for a fiscal position' — these are direct write operations that modify fiscal/tax configuration in Odoo's Bulgarian localization module (l10n_bg_tax_admin).
Documented attack patterns abuse exactly the kind of access odoo_fp_configure 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_configure:
{
"version": "1",
"default": "deny",
"tools": {
"odoo_fp_configure": {
"limits": [
{
"counter": "odoo_fp_configure_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} odoo_fp_configure stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add or update a tax action map entry for a fiscal position (l10n_bg_tax_admin). 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.
Register the Odoo Claude MCP server in PolicyLayer and add a rule for odoo_fp_configure: 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_configure is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the odoo_fp_configure 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_configure. 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_configure 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.