stateset_update_work_order_task
Updates an individual task within a work order. Track task progress and completion.
This record as markdown: /tools/stateset-mcp-server/stateset-update-work-order-task.md
What stateset_update_work_order_task does on Stateset
AI agents use stateset_update_work_order_task 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_update_work_order_task is rated Medium
This tool modifies task data within a work order (status, progress, completion state) but does not delete or destroy data. The update is reversible—task states can be changed again. While the tool could impact workflow operations if misused (e.g., marking tasks complete prematurely), it lacks the irreversibility of Destructive operations, the external execution risk of Execute, or financial impact.
From the tool's definition Tool description states 'Updates an individual task within a work order' — the word 'Updates' indicates modification of existing data. The purpose 'Track task progress and completion' confirms reversible state changes to task records.
Attacks that exploit this kind of access
The rule that runs stateset_update_work_order_task 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_update_work_order_task, this is the rule to start with:
stateset_update_work_order_task 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_update_work_order_task call is checked against it from then on.
Questions about stateset_update_work_order_task
Updates an individual task within a work order. Track task progress and completion. 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_update_work_order_task: 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_update_work_order_task 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_update_work_order_task 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_update_work_order_task. 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_update_work_order_task 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