Remove ingredients from your bar shelf by their IDs
AI agents call remove_ingredients_from_shelf to permanently remove resources in Bar Assistant MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing ingredients from the shelf deletes/purges those entries from the user's bar inventory. The action is described as 'remove' which implies irreversible deletion of those shelf items. While not catastrophic (data could potentially be re-added), it is a destructive operation that cannot be automatically undone. Severity is medium as it affects only bar inventory data, not critical systems.
From the tool's definition Remove ingredients from your bar shelf by their IDs
Attacks that exploit this kind of access
Remove ingredients from your bar shelf by their IDs. It is categorised as a Destructive tool in the Bar Assistant MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bar Assistant MCP Server MCP server in PolicyLayer and add a rule for remove_ingredients_from_shelf: 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 Bar Assistant MCP Server. Nothing to install.
remove_ingredients_from_shelf 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 remove_ingredients_from_shelf 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 remove_ingredients_from_shelf. 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.
remove_ingredients_from_shelf is provided by the Bar Assistant MCP Server MCP server (the-real-py/bar-assistant-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 →