stateset_assign_work_order
Assigns a work order to a specific user or team. The assignee will be responsible for completing the work order tasks.
This record as markdown: /tools/stateset-mcp-server/stateset-assign-work-order.md
What stateset_assign_work_order does on Stateset
AI agents use stateset_assign_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_assign_work_order is rated Medium
The tool creates or modifies metadata (assignment ownership) on an existing work order. This is a write operation with business logic implications—assigning work to the wrong person could disrupt operations—but it is fully reversible (can be reassigned). It does not delete data, execute code, or move money, so it does not rise to Destructive, Execute, or Financial categories.
From the tool's definition Tool description states it 'Assigns a work order to a specific user or team', which modifies the assignment state of a work order record. This is a reversible data modification operation.
Attacks that exploit this kind of access
The rule that runs stateset_assign_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_assign_work_order, this is the rule to start with:
stateset_assign_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_assign_work_order call is checked against it from then on.
Questions about stateset_assign_work_order
Assigns a work order to a specific user or team. The assignee will be responsible for completing the work order tasks. 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_assign_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_assign_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_assign_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_assign_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_assign_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