Search for pages by content within a specific Collective. Returns matching page metadata.
AI agents call search_in_collective 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 performs a search operation that queries existing pages and returns metadata results. It has no side effects—it does not create, modify, delete, or execute any operations. The returned data is read-only retrieval from the Nextcloud Collectives system. No user data is at risk of unintended modification or deletion through misuse of this tool.
From the tool's definition Tool name 'search_in_collective' and description 'Search for pages by content within a specific Collective. Returns matching page metadata.' indicate a query operation that retrieves and returns data without modifying or executing actions.
Attacks that exploit this kind of access
Search for pages by content within a specific Collective. Returns matching page metadata. 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 search_in_collective: 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.
search_in_collective 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 search_in_collective 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 search_in_collective. 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.
search_in_collective 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 →