This record as markdown: /tools/app-businys-mcp-server/delete-gear-item.md
What delete_gear_item does on Businys
AI agents call delete_gear_item to permanently remove resources in Businys, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_gear_item is rated Critical
This tool removes gear items from a business inventory system. Even though implemented as a soft delete (technically reversible), from the perspective of normal business operations and an AI agent's capability, this is a destructive action—the item disappears from the professional's active inventory.
From the tool's definition Tool name is 'delete_gear_item' and description states 'soft delete', indicating removal of data records from active use. Despite being a soft delete (reversible at database level), the user-facing action is irreversible deletion.
Attacks that exploit this kind of access
The rule that runs delete_gear_item safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_gear_item, this is the rule to start with:
delete_gear_item is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Businys, apply this rule, and every delete_gear_item call is checked against it from then on.
Questions about delete_gear_item
Archive a gear item (soft delete). It is categorised as a Destructive tool in the Businys MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Businys MCP server in PolicyLayer and add a rule for delete_gear_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 Businys. Nothing to install.
delete_gear_item 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 delete_gear_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 delete_gear_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.
delete_gear_item is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
Across the catalogue