snow_request_approval
Create a sysapproval_approver record asking a specific user to approve a record on a source table. Sets state to
This record as markdown: /tools/serac/snow-request-approval.md
What snow_request_approval does on Serac
AI agents use snow_request_approval 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_request_approval is rated Medium
Creating approval records is a reversible write operation (the record can be modified or deleted). However, it escalates to 'high' severity because it engages workflow authorization infrastructure in an enterprise system—an AI agent could create fraudulent approval requests, bypass normal change control, or request unwarranted approvals at scale, with significant business impact even though the action itself is not…
From the tool's definition Tool description states it "Create[s] a sysapproval_approver record", which is an explicit write operation that creates new data in the ServiceNow system. The incomplete description cuts off mid-sentence at "Sets state to", but the creation action is clear.
Attacks that exploit this kind of access
The rule that runs snow_request_approval 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_request_approval, this is the rule to start with:
snow_request_approval 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_request_approval call is checked against it from then on.
Questions about snow_request_approval
Create a sysapproval_approver record asking a specific user to approve a record on a source table. Sets state to. 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_request_approval: 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_request_approval 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_request_approval 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_request_approval. 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_request_approval 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