This record as markdown: /tools/serac/snow-approve-reject.md
What snow_approve_reject does on Serac
AI agents use snow_approve_reject 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_reject is rated Medium
This tool modifies approval request states reversibly within a workflow system. It is Write (not Execute) because it updates data rather than running arbitrary code. It is not Destructive because approval decisions are reversible (can be re-evaluated or overridden by other actors).
From the tool's definition Tool name 'snow_approve_reject' and description 'Approve or reject approval request' indicate state-changing actions that modify workflow approval records in ServiceNow.
Attacks that exploit this kind of access
The rule that runs snow_approve_reject 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_reject, this is the rule to start with:
snow_approve_reject 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_reject call is checked against it from then on.
Questions about snow_approve_reject
Approve or reject approval request. 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_reject: 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_reject 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_reject 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_reject. 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_reject 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