stateset_receive_purchase_order
Records receipt of items from a purchase order. Specify quantities received for each item. Updates inventory automatically.
This record as markdown: /tools/stateset-mcp-server/stateset-receive-purchase-order.md
What stateset_receive_purchase_order does on Stateset
AI agents use stateset_receive_purchase_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_receive_purchase_order is rated Medium
This tool modifies system state by recording purchase order receipts and automatically updating inventory levels. While it writes data (Write category), the severity is high because incorrect inventory updates could disrupt supply chain operations, order fulfillment, and financial reconciliation. An AI agent misusing this could create ghost inventory or hide stock, impacting business operations significantly.
From the tool's definition Tool description states it 'Records receipt of items from a purchase order' and 'Updates inventory automatically.' The verbs 'Records' and 'Updates' indicate data modification operations.
Attacks that exploit this kind of access
The rule that runs stateset_receive_purchase_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_receive_purchase_order, this is the rule to start with:
stateset_receive_purchase_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_receive_purchase_order call is checked against it from then on.
Questions about stateset_receive_purchase_order
Records receipt of items from a purchase order. Specify quantities received for each item. Updates inventory automatically. 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_receive_purchase_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_receive_purchase_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_receive_purchase_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_receive_purchase_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_receive_purchase_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