List all Collectives the authenticated user has access to. Returns id, name, slug, emoji, and permission levels.
AI agents call list_collectives 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 queries and returns metadata about collectives accessible to the user (id, name, slug, emoji, permission levels) without modifying, deleting, or executing any operations. It is a straightforward read/list operation, consistent with the Read category.
From the tool's definition Tool name is 'list_collectives' and description states it 'List all Collectives the authenticated user has access to. Returns id, name, slug, emoji, and permission levels.' This is a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all Collectives the authenticated user has access to. Returns id, name, slug, emoji, and permission levels. 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_collectives: 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_collectives 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_collectives 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_collectives. 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_collectives 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 →