AI agents use add_shopping_item to create or update resources in Pantrist — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pantrist environment.
This tool creates or adds data to the shopping list without deleting or executing arbitrary operations. The modification is reversible (items can be removed with delete_shopping_item). The blast radius of misuse is minimal — an attacker could add unwanted items to a shopping list, causing minor inconvenience but no financial loss, data destruction, or external command execution.
From the tool's definition Tool name is 'add_shopping_item' and description states 'Add an item to the shopping list' — this creates a new entry in the shopping list, which is a reversible modification of data.
Attacks that exploit this kind of access
Add an item to the shopping list by name. The API matches. It is categorised as a Write tool in the Pantrist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pantrist MCP server in PolicyLayer and add a rule for add_shopping_item: 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 Pantrist. Nothing to install.
add_shopping_item 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 add_shopping_item 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 add_shopping_item. 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.
add_shopping_item is provided by the Pantrist MCP server (pantrist-dev/pantrist-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 →