approve_request
Approve a pending approval request (requires WRITE_ENABLED=true)
This record as markdown: /tools/tedorigawa001-servicenow-mcp/approve-request.md
What approve_request does on ServiceNow-MCP
AI agents use approve_request to create or update resources in ServiceNow-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow-MCP environment.
Why approve_request is rated Medium
Approving a request is a reversible write operation that changes the approval status. While it alters workflow state and may trigger downstream processes, it is not destructive (the approval can be revoked/withdrawn), not financial (no money moves), and not execute-level code/script execution. The impact depends on what the request controls, but the tool itself performs approval state modification.
From the tool's definition Tool description states 'Approve a pending approval request' which modifies the state of an approval record from pending to approved. The requirement for 'WRITE_ENABLED=true' confirms this performs data modification.
Attacks that exploit this kind of access
The rule that runs approve_request safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For approve_request, this is the rule to start with:
approve_request 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 ServiceNow-MCP, apply this rule, and every approve_request call is checked against it from then on.
Questions about approve_request
Approve a pending approval request (requires WRITE_ENABLED=true). It is categorised as a Write tool in the ServiceNow-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow MCP server in PolicyLayer and add a rule for approve_request: 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 ServiceNow-MCP. Nothing to install.
approve_request 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 approve_request 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 approve_request. 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.
approve_request is provided by the ServiceNow MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow, and thousands of servers like it.
This server
Across the catalogue