close_order · AdminAgent MCP: Risk & Policy

WHAT IT DOES

What close_order does on AdminAgent

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

WHY IT NEEDS A POLICY

Why close_order needs a policy

Closing/archiving an order changes its state and visibility in the system but does not delete data or prevent undo. This is a state modification (Write) rather than Destructive. However, severity is high because misuse could disrupt order management workflows, reconciliation processes, and customer service operations for an entire store.

From the tool's definition Tool description states 'Close/archive an order' — this modifies order state from active to closed/archived, which is reversible (orders can be reopened or unarchived in most e-commerce systems).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_order Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "close_order": {
      "limits": [
        {
          "counter": "close_order_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 AdminAgent, so you can run agents against it safely.

FAQ

Questions about close_order

What does the close_order tool do? +

Close/archive an order. It is categorised as a Write tool in the AdminAgent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on close_order? +

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

What risk level is close_order? +

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

Can I rate-limit close_order? +

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

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

close_order is provided by the AdminAgent MCP server (rushikeshmore/admin-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.