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).
AI agents call get_collection to retrieve information from Ssakone Pocketbase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves schema and access control information from PocketBase collections. While categorically a Read operation, the severity is elevated to 'high' because access rules and schema details are sensitive information that could be exploited to identify attack surfaces or privilege escalation opportunities. An AI agent could use this information to craft targeted attacks against the PocketBase instance.
From the tool's definition Tool description states it 'Get[s] detailed information about a specific collection' and 'Returns complete schema including field definitions, types, constraints, and access rules'. These are read operations with no modification or deletion.
Attacks that exploit this kind of access
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 Ssakone Pocketbase MCP Server, which means it retrieves data without modifying state.
Register the Ssakone Pocketbase 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 Ssakone Pocketbase. Nothing to install.
get_collection 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 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.
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.
get_collection is provided by the Ssakone Pocketbase MCP server (@iflow-mcp/ssakone-pocketbase-mcp-server). 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 →