list_collections
List all data collections (tables) for an agent. Shows schema and record counts.
This record as markdown: /tools/io-github-proagentstore-platform/list-collections.md
What list_collections does on ProAgentStore
AI agents call list_collections to retrieve information from ProAgentStore without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_collections is rated Low
This tool retrieves schema information and metadata about existing collections—purely informational with no side effects. It does not create, modify, delete, or execute operations. The low severity reflects the limited blast radius of exposing collection structure information; while schema details could inform an attack, the tool itself performs no destructive or consequential actions.
From the tool's definition Tool name is 'list_collections' and description states it 'List all data collections (tables) for an agent. Shows schema and record counts.' The verbs 'list' and 'shows' indicate read-only retrieval of metadata without modification.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs list_collections safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_collections, this is the rule to start with:
list_collections is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every list_collections call is checked against it from then on.
Questions about list_collections
List all data collections (tables) for an agent. Shows schema and record counts. It is categorised as a Read tool in the ProAgentStore MCP Server, which means it retrieves data without modifying state.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for list_collections: 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 ProAgentStore. Nothing to install.
list_collections 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_collections 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_collections. 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_collections is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ProAgentStore, and thousands of servers like it.
This server
Across the catalogue