snow_request_approval · Serac MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why snow_request_approval needs a policy

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

Recommended rule Ready

Verdict

snow_request_approval Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "snow_request_approval": {
      "limits": [
        {
          "counter": "snow_request_approval_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Serac, so you can run agents against it safely.

FAQ

Questions about snow_request_approval

What does the snow_request_approval tool do? +

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.

How do I enforce a policy on snow_request_approval? +

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.

What risk level is snow_request_approval? +

snow_request_approval is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit snow_request_approval? +

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.

How do I block snow_request_approval completely? +

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.

What MCP server provides snow_request_approval? +

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.