Move a document to trash
AI agents call trash_document to permanently remove resources in Basecamp MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Moving a document to trash is a destructive action that removes the document from its accessible location. While trash can sometimes be recovered, trashing is typically considered a destructive/deletion operation. The term 'trash' implies the document is being marked for deletion or removed from normal access, which is irreversible in many systems without explicit recovery steps.
From the tool's definition Move a document to trash
Attacks that exploit this kind of access
Move a document to trash. It is categorised as a Destructive tool in the Basecamp MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Basecamp MCP Server MCP server in PolicyLayer and add a rule for trash_document: 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 Basecamp MCP Server. Nothing to install.
trash_document 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 trash_document 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 trash_document. 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.
trash_document is provided by the Basecamp MCP Server MCP server (jhliberty/basecamp-mcp-server). 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 →