stateset_hold_work_order
Places a work order on hold. Use when work cannot continue due to missing materials, pending decisions, or other blockers. Requires a reason.
This record as markdown: /tools/stateset-mcp-server/stateset-hold-work-order.md
What stateset_hold_work_order does on Stateset
AI agents use stateset_hold_work_order to create or update resources in Stateset, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stateset environment.
Why stateset_hold_work_order is rated Medium
This tool modifies work order state (status change to 'hold') but is reversible — the work order can be resumed or unblocked. It does not delete data or trigger irreversible destruction, nor does it execute arbitrary code or involve financial transactions.
From the tool's definition Tool description states 'Places a work order on hold' — a state-changing operation that modifies work order status. The verb 'places' and the requirement for 'a reason' indicate this creates or updates work order records.
Attacks that exploit this kind of access
The rule that runs stateset_hold_work_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_hold_work_order, this is the rule to start with:
stateset_hold_work_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Stateset, apply this rule, and every stateset_hold_work_order call is checked against it from then on.
Questions about stateset_hold_work_order
Places a work order on hold. Use when work cannot continue due to missing materials, pending decisions, or other blockers. Requires a reason. It is categorised as a Write tool in the Stateset MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Stateset MCP server in PolicyLayer and add a rule for stateset_hold_work_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_hold_work_order is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the stateset_hold_work_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_hold_work_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_hold_work_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.
This server
Across the catalogue