Add a catalog item to the shopping cart
AI agents use catalog_add_to_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.
This tool modifies cart data by adding items, which is a reversible write operation. While it doesn't execute code or delete data, it does commit actions that could have downstream consequences (e.g., unintended procurement requests if chained to checkout). The severity is medium rather than high because the action is containable—items can be removed from carts before checkout.
From the tool's definition Tool name 'catalog_add_to_cart' and description 'Add a catalog item to the shopping cart' indicate a modification action that creates or updates cart state.
Attacks that exploit this kind of access
Add a catalog item to the shopping cart. 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_add_to_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_add_to_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_add_to_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_add_to_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_add_to_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 →