Alter an existing sales order in Omie ERP
AI agents use update_sales_order to create or update resources in Mcp Afip — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Afip environment.
The tool creates or modifies data reversibly (Write category), not irreversibly (Destructive) or financial movements themselves. However, since sales orders are critical business documents in a tax/invoicing context (AFIP is the Argentine tax authority), misuse could have significant downstream effects on financial records, justifying 'high' severity.
From the tool's definition Tool name contains 'update' and description states 'Alter an existing sales order' — both indicate modification of data. Sales orders are financial documents in an ERP system, but the tool modifies (not deletes) them reversibly.
Documented attack patterns abuse exactly the kind of access update_sales_order gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Afip, and nothing reaches the server without passing your rules. This is the rule we recommend for update_sales_order:
{
"version": "1",
"default": "deny",
"tools": {
"update_sales_order": {
"limits": [
{
"counter": "update_sales_order_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} update_sales_order 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.
Alter an existing sales order in Omie ERP. It is categorised as a Write tool in the Mcp Afip MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for update_sales_order: 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 Mcp Afip. Nothing to install.
update_sales_order 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 update_sales_order 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 update_sales_order. 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.
update_sales_order is provided by the Mcp Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Afip, 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.
1300 Mcp Afip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.