Manage warehouses in Pancake POS. Actions: list, get, create, update, delete.
AI agents call manage_warehouses to permanently remove resources in Pancake POS MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly includes a 'delete' action for warehouse management. Since warehouses are core operational entities in a POS system (tied to inventory, orders, and fulfillment), deleting one could be irreversible and have significant blast radius. Per the rules, when a tool spans categories, the most severe applicable category wins — Destructive supersedes Write and Read.
From the tool's definition Actions: list, get, create, update, delete
Attacks that exploit this kind of access
Manage warehouses in Pancake POS. Actions: list, get, create, update, delete. It is categorised as a Destructive tool in the Pancake POS MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pancake POS MCP server in PolicyLayer and add a rule for manage_warehouses: 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 Pancake POS MCP. Nothing to install.
manage_warehouses 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 manage_warehouses 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 manage_warehouses. 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.
manage_warehouses is provided by the Pancake POS MCP server (svn4pro/pancake-pos-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 →