This record as markdown: /tools/stateset-mcp-server/stateset-delete-order.md
What stateset_delete_order does on Stateset
AI agents call stateset_delete_order to permanently remove resources in Stateset, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why stateset_delete_order is rated Critical
Deletion of an order record is a destructive operation that cannot be undone. It irreversibly removes data from the system, potentially affecting financial records, audit trails, customer history, and business continuity. This poses critical risk if an AI agent misuses it without proper authorization or context, as it could destroy important business data.
From the tool's definition Tool name and description state: 'Deletes an order record'. The verb 'delete' is explicitly destructive and irreversible.
Attacks that exploit this kind of access
The rule that runs stateset_delete_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stateset, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stateset_delete_order, this is the rule to start with:
stateset_delete_order is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Stateset, apply this rule, and every stateset_delete_order call is checked against it from then on.
Questions about stateset_delete_order
Deletes an order record. It is categorised as a Destructive tool in the Stateset MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Stateset MCP server in PolicyLayer and add a rule for stateset_delete_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 Stateset. Nothing to install.
stateset_delete_order is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the stateset_delete_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 stateset_delete_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.
stateset_delete_order is provided by the Stateset MCP server (stateset/stateset-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stateset, and thousands of servers like it.
Across the catalogue