snow_approve_procurement
Mark a procurement request (proc_request) as approved, with optional comments. Use after the request has been reviewed — advances it toward purchase-order creation.
This record as markdown: /tools/serac/snow-approve-procurement.md
What snow_approve_procurement does on Serac
AI agents use snow_approve_procurement to create or update resources in Serac, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Serac environment.
Why snow_approve_procurement is rated Medium
Classified as Write rather than Financial because the tool itself approves a request without directly moving money. However, high severity is appropriate because approval directly triggers financial obligations (PO creation) and procurement spend authorization in an enterprise system. The reversibility of the approval action (vs. irreversible deletion) distinguishes it from Destructive.
From the tool's definition Tool marks a procurement request as approved and 'advances it toward purchase-order creation.' This modifies procurement state and triggers downstream financial processes (purchase-order creation), but the approval action itself is reversible (can be…
Attacks that exploit this kind of access
The rule that runs snow_approve_procurement 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_approve_procurement, this is the rule to start with:
snow_approve_procurement 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 Serac, apply this rule, and every snow_approve_procurement call is checked against it from then on.
Questions about snow_approve_procurement
Mark a procurement request (proc_request) as approved, with optional comments. Use after the request has been reviewed — advances it toward purchase-order creation. It is categorised as a Write tool in the Serac MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Serac MCP server in PolicyLayer and add a rule for snow_approve_procurement: 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_approve_procurement 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 snow_approve_procurement 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_approve_procurement. 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_approve_procurement 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.
This server
Across the catalogue