update_order_status

Update the status of a shop order (e.g. confirm, ship, cancel).

SERVERFavCRM SOURCEhttps://api.favcrm.io/mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-favcrm-favcrm/update-order-status.md

WHAT IT DOES

What update_order_status does on FavCRM

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

Parameter	Type	Required	Description
`status`	string	Yes	New order status
`orderId`	string	Yes	The order UUID

Parameters from the server's own tool schema.

RISK

Why update_order_status is rated Medium

This tool modifies existing order records by changing their status. While 'cancel' might seem destructive, the description frames it as a status update rather than irreversible deletion—the order record persists, only its state changes. This is a Write operation.

From the tool's definition Tool name 'update_order_status' and description 'Update the status of a shop order (e.g. confirm, ship, cancel)' indicate modification of order data. The examples (confirm, ship, cancel) are reversible state transitions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_order_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_order_status, this is the rule to start with:

update_order_status Rate-limited

update_order_status 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_order_status": {
      "limits": [
        {
          "counter": "update_order_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every update_order_status call is checked against it from then on.

FAQ

Questions about update_order_status

What does the update_order_status tool do? +

Update the status of a shop order (e.g. confirm, ship, cancel). It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_order_status accept? +

update_order_status accepts 2 parameters: status, orderId. Required: status, orderId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_order_status? +

Register the FavCRM MCP server in PolicyLayer and add a rule for update_order_status: 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 FavCRM. Nothing to install.

What risk level is update_order_status? +

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

Can I rate-limit update_order_status? +

Yes. Add a rate_limit block to the update_order_status 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_order_status completely? +

Set action: deny in the PolicyLayer policy for update_order_status. 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_order_status? +

update_order_status is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FavCRM, and thousands of servers like it.

This server

All 220 FavCRM tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →