This record as markdown: /tools/openclaw/drop.md
What drop does on OpenClaw
AI agents call drop to permanently remove resources in OpenClaw, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why drop is rated Critical
The tool removes or deletes a policy, which is an irreversible action that cannot be undone. This qualifies as Destructive rather than Write (which is reversible). The confidence is 0.85 rather than higher because the description is minimal and lacks specifics about scope, but the semantic meaning of 'drop' in data/policy contexts is unambiguous.
From the tool's definition Tool name 'drop' combined with description 'drop policy' indicates deletion of a policy object. 'Drop' is a destructive verb that permanently removes data.
Attacks that exploit this kind of access
The rule that runs drop safely
PolicyLayer is an MCP gateway: it sits between your AI agents and OpenClaw, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For drop, this is the rule to start with:
drop 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 OpenClaw, apply this rule, and every drop call is checked against it from then on.
Questions about drop
drop policy. It is categorised as a Destructive tool in the OpenClaw MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OpenClaw MCP server in PolicyLayer and add a rule for drop: 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 OpenClaw. Nothing to install.
drop 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 drop 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 drop. 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.
drop is provided by the OpenClaw MCP server (openclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on OpenClaw, and thousands of servers like it.
Across the catalogue