Low Risk

list_collections

Get the list of all collections from PocketBase. Returns collection names, types, and basic metadata including created/updated timestamps.

How to control list_collections ↓

AI agents call list_collections to retrieve information from PocketBase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and retrieves metadata about collections without side effects. It is a pure read operation that returns information only. Even though the parent server enables administrative operations, this specific tool is narrowly scoped to data retrieval. Low severity because listing collections reveals schema structure but does not access sensitive data, execute code, or modify state.

From the tool's definition Tool name and description explicitly state 'Get the list of all collections' and 'Returns collection names, types, and basic metadata'. No modification, deletion, or execution capability is described.

Documented attack patterns abuse exactly the kind of access list_collections gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and PocketBase MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_collections:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_collections": {}
  }
}

list_collections is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register PocketBase MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the list_collections tool do? +

Get the list of all collections from PocketBase. Returns collection names, types, and basic metadata including created/updated timestamps. It is categorised as a Read tool in the PocketBase MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_collections? +

Register the PocketBase MCP Server 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 PocketBase MCP Server. Nothing to install.

What risk level is list_collections? +

list_collections is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_collections? +

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.

How do I block list_collections completely? +

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.

What MCP server provides list_collections? +

list_collections is provided by the PocketBase MCP Server MCP server (ssakone/pb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PocketBase MCP Server tool call.

Deterministic rules across all 19 PocketBase MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

19 PocketBase MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.