Low Risk

get_collection

Get detailed information about a specific collection from PocketBase. Returns complete schema including field definitions, types, constraints, and access rules (listRule, viewRule, createRule, updateRule, deleteRule).

How to control get_collection ↓

AI agents call get_collection 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 is a Read operation: it queries and retrieves collection schema information with no side effects. Severity is elevated to medium (rather than low) because the returned access rules and schema details could be sensitive information useful for planning attacks, though the tool itself performs no destructive or write operations.

From the tool's definition Tool explicitly 'Returns complete schema including field definitions, types, constraints, and access rules' — retrieves metadata about collections without modification.

Documented attack patterns abuse exactly the kind of access get_collection 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 get_collection:

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

get_collection 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 get_collection tool do? +

Get detailed information about a specific collection from PocketBase. Returns complete schema including field definitions, types, constraints, and access rules (listRule, viewRule, createRule, updateRule, deleteRule). 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 get_collection? +

Register the PocketBase MCP Server MCP server in PolicyLayer and add a rule for get_collection: 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 get_collection? +

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

Can I rate-limit get_collection? +

Yes. Add a rate_limit block to the get_collection 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 get_collection completely? +

Set action: deny in the PolicyLayer policy for get_collection. 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 get_collection? +

get_collection 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.