cancel_request
Cancel an open service catalog request (requires WRITE_ENABLED=true)
This record as markdown: /tools/tedorigawa001-servicenow-mcp/cancel-request.md
What cancel_request does on ServiceNow-MCP
AI agents call cancel_request to permanently remove resources in ServiceNow-MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cancel_request is rated Critical
Cancelling a service catalog request is effectively irreversible: once cancelled, the request workflow is terminated and any associated approvals, tasks, or fulfillment steps are aborted. While the record still exists, the business process cannot easily be resumed from the same state, making this closer to Destructive than a simple Write.
From the tool's definition 'Cancel an open service catalog request' — cancelling a request is an irreversible state change that terminates the request workflow; 'requires WRITE_ENABLED=true' confirms it performs a state-modifying action
Attacks that exploit this kind of access
The rule that runs cancel_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 cancel_request, this is the rule to start with:
cancel_request is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every cancel_request call is checked against it from then on.
Questions about cancel_request
Cancel an open service catalog request (requires WRITE_ENABLED=true). It is categorised as a Destructive tool in the ServiceNow-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ServiceNow MCP server in PolicyLayer and add a rule for cancel_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.
cancel_request is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_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 cancel_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.
cancel_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.
Across the catalogue