remove_item
AI agents call remove_item to permanently remove resources in DM20 Protocol — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'remove_item' strongly suggests irreversible removal of an item (likely from a character's inventory or the world state). Given sibling tools like 'add_item_to_character', this is likely the inverse operation — a destructive action that deletes data. However, the empty description lowers confidence, as it could potentially be a soft removal or temporary action.
From the tool's definition Tool name 'remove_item' implies deletion of an item from a character or inventory; description is empty and uninformative.
Attacks that exploit this kind of access
remove_item. It is categorised as a Destructive tool in the DM20 Protocol MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DM20 Protocol MCP server in PolicyLayer and add a rule for remove_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 DM20 Protocol. Nothing to install.
remove_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 remove_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 remove_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.
remove_item is provided by the DM20 Protocol MCP server (polloinfilzato/dm20-protocol). 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 →