stateset_start_work_order

Starts work on a work order. Changes status from assigned to in-progress. Use when beginning actual production or service work.

SERVERStateset SOURCEstateset/stateset-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/stateset-mcp-server/stateset-start-work-order.md

WHAT IT DOES

What stateset_start_work_order does on Stateset

AI agents invoke stateset_start_work_order to trigger actions in Stateset. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why stateset_start_work_order is rated High

This tool triggers a state transition in an external system (work order management), which is an operation with real-world consequences. While not destructive (the change is reversible via status updates), it executes a significant business action that could affect production workflows, resource allocation, and downstream processes.

From the tool's definition Starts work on a work order. Changes status from assigned to in-progress.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stateset_start_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_start_work_order, this is the rule to start with:

stateset_start_work_order Rate-limited

stateset_start_work_order stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stateset_start_work_order": {
      "limits": [
        {
          "counter": "stateset_start_work_order_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Stateset, apply this rule, and every stateset_start_work_order call is checked against it from then on.

FAQ

Questions about stateset_start_work_order

What does the stateset_start_work_order tool do? +

Starts work on a work order. Changes status from assigned to in-progress. Use when beginning actual production or service work. It is categorised as a Execute tool in the Stateset MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stateset_start_work_order? +

Register the Stateset MCP server in PolicyLayer and add a rule for stateset_start_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.

What risk level is stateset_start_work_order? +

stateset_start_work_order is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit stateset_start_work_order? +

Yes. Add a rate_limit block to the stateset_start_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.

How do I block stateset_start_work_order completely? +

Set action: deny in the PolicyLayer policy for stateset_start_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.

What MCP server provides stateset_start_work_order? +

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

KEEP EXPLORING

More on Stateset, and thousands of servers like it.

This server

All 238 Stateset tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP →start_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →