Medium Risk

update_sales_order

Alter an existing sales order in Omie ERP

How to control update_sales_order ↓

What update_sales_order does on Mcp Ap2

AI agents use update_sales_order to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.

Medium Risk

Why update_sales_order needs a policy

This tool modifies an existing sales order reversibly (orders can be updated multiple times, and changes are not permanently destructive). It is a Write operation rather than Destructive because updating does not irreversibly delete or remove the order. In an e-commerce/payment context, unauthorized modification of sales orders could impact order fulfillment and customer records, warranting medium severity.

From the tool's definition Tool name: update_sales_order. Description: 'Alter an existing sales order in Omie ERP'. The verb 'alter' indicates modification of existing data (sales order).

Documented attack patterns abuse exactly the kind of access update_sales_order gives an agent:

How to control update_sales_order

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for update_sales_order:

policy.json
{
  "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.

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about update_sales_order

What does the update_sales_order tool do? +

Alter an existing sales order in Omie ERP. It is categorised as a Write tool in the Mcp Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_sales_order? +

Register the Mcp Ap2 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 Ap2. Nothing to install.

What risk level is update_sales_order? +

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

Can I rate-limit update_sales_order? +

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.

How do I block update_sales_order completely? +

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.

What MCP server provides update_sales_order? +

update_sales_order is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, 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 Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.