Submit/checkout the shopping cart to create requests
AI agents use catalog_submit_cart to create or update resources in ServiceNow MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow MCP Server environment.
The tool creates new request records in ServiceNow, which is a reversible write operation. While it commits a user's selections, it does not delete data (not Destructive), does not directly move money (not Financial), and does not execute arbitrary code (not Execute).
From the tool's definition Tool name 'catalog_submit_cart' and description 'Submit/checkout the shopping cart to create requests' indicate the tool creates service requests in ServiceNow by committing a shopping cart selection.
Attacks that exploit this kind of access
Submit/checkout the shopping cart to create requests. It is categorised as a Write tool in the ServiceNow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for catalog_submit_cart: 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 Server. Nothing to install.
catalog_submit_cart 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 catalog_submit_cart 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 catalog_submit_cart. 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.
catalog_submit_cart is provided by the ServiceNow MCP Server MCP server (schwarztim/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →