snow_create_purchase_order
Open a purchase order (proc_po) against a vendor, with optional requested_by user and total_cost. Captures the buy-side step after a procurement request has been approved.
This record as markdown: /tools/serac/snow-create-purchase-order.md
What snow_create_purchase_order does on Serac
AI agents use snow_create_purchase_order to commit financial operations through Serac, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why snow_create_purchase_order is rated Critical
Creating a purchase order is a financial commitment — it binds the organization to pay a vendor for goods or services. This directly falls under the Financial category as it moves money or commits financial obligations. Misuse could result in unauthorized procurement commitments of arbitrary value.
From the tool's definition Open a purchase order (proc_po) against a vendor, with optional requested_by user and total_cost. Captures the buy-side step after a procurement request has been approved.
Attacks that exploit this kind of access
The rule that runs snow_create_purchase_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snow_create_purchase_order, this is the rule to start with:
Any call to snow_create_purchase_order is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Serac, apply this rule, and every snow_create_purchase_order call is checked against it from then on.
Questions about snow_create_purchase_order
Open a purchase order (proc_po) against a vendor, with optional requested_by user and total_cost. Captures the buy-side step after a procurement request has been approved. It is categorised as a Financial tool in the Serac MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Serac MCP server in PolicyLayer and add a rule for snow_create_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 Serac. Nothing to install.
snow_create_purchase_order is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the snow_create_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 snow_create_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.
snow_create_purchase_order is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Serac, and thousands of servers like it.
Across the catalogue