horoshop_update_order_status · Horoshop MCP: Risk & Policy

WHAT IT DOES

What horoshop_update_order_status does on Horoshop

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

WHY IT NEEDS A POLICY

Why horoshop_update_order_status needs a policy

The tool modifies order status through the Horoshop e-commerce API. Status updates are Write operations as they change data state reversibly (status can be updated again). Severity is high because misuse could disrupt order fulfillment workflows, customer communications, and business operations, though the change is theoretically reversible.

From the tool's definition Tool name contains 'update' and description states it 'Updates an order status', indicating modification of existing order data. This is a reversible state change operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

horoshop_update_order_status Rate-limited

horoshop_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": {
    "horoshop_update_order_status": {
      "limits": [
        {
          "counter": "horoshop_update_order_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Horoshop, so you can run agents against it safely.

FAQ

Questions about horoshop_update_order_status

What does the horoshop_update_order_status tool do? +

Updates an order status using the Horoshop API. It is categorised as a Write tool in the Horoshop MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on horoshop_update_order_status? +

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

What risk level is horoshop_update_order_status? +

horoshop_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 horoshop_update_order_status? +

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

Set action: deny in the PolicyLayer policy for horoshop_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 horoshop_update_order_status? +

horoshop_update_order_status is provided by the Horoshop MCP server (narkov/horoshop-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.