List pages in the trash for a Collective. These can be restored or permanently purged.
AI agents call list_trashed_pages to retrieve information from Collectives without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only lists/retrieves pages currently in trash. The mention of 'restored or permanently purged' describes what can be done with the results, not what this tool does. It performs a read-only query with no side effects.
From the tool's definition 'List pages in the trash' — this is a retrieval operation that queries trashed pages without modifying or deleting anything.
Attacks that exploit this kind of access
List pages in the trash for a Collective. These can be restored or permanently purged. It is categorised as a Read tool in the Collectives MCP Server, which means it retrieves data without modifying state.
Register the Collectives MCP server in PolicyLayer and add a rule for list_trashed_pages: 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 Collectives. Nothing to install.
list_trashed_pages 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 list_trashed_pages 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 list_trashed_pages. 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.
list_trashed_pages is provided by the Collectives MCP server (megamaced/nc_collectives-mcp). 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 →