List recently-modified pages for a Collective, ordered by last edit time.
AI agents call list_recent_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.
This tool retrieves metadata about pages (their recent modification status) from a Nextcloud Collectives instance. It performs a read-only query with no ability to modify, delete, or execute operations. The blast radius of misuse is minimal—an attacker could learn what pages exist and their modification timeline, but cannot alter or delete content. This is a clear Read operation.
From the tool's definition Tool name 'list_recent_pages' and description 'List recently-modified pages' indicate a query/retrieval operation with no side effects. The description explicitly states the action is to list (retrieve and order) existing data.
Attacks that exploit this kind of access
List recently-modified pages for a Collective, ordered by last edit time. 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_recent_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_recent_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_recent_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_recent_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_recent_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 →