AI agents call get_trash to retrieve information from Things 3 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves already-deleted (trashed) task items from Things 3. It performs a read-only query operation with no ability to modify, execute, or permanently destroy data. The blast radius is minimal since it only exposes information about items that have already been removed from active use. Confidence is high because the intent and function are unambiguous.
From the tool's definition Tool name is 'get_trash' and description states 'Get trashed todos' — a retrieval/query operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_trash gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Things 3 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_trash:
{
"version": "1",
"default": "deny",
"tools": {
"get_trash": {}
}
}get_trash is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get trashed todos. It is categorised as a Read tool in the Things 3 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Things 3 MCP Server MCP server in PolicyLayer and add a rule for get_trash: 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 Things 3 MCP Server. Nothing to install.
get_trash is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_trash 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 get_trash. 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.
get_trash is provided by the Things 3 MCP Server MCP server (rossshannon/things3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 Things 3 MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
24 Things 3 MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.