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.
The tool retrieves metadata about a collection in a PocketBase database. This is a read-only query operation that does not create, modify, delete, or execute external operations. It has minimal blast radius as it only exposes database schema information.
From the tool's definition Tool name 'get_collection' and description 'Get details for a collection' indicate a retrieval operation with no data modification or side effects.
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:
{
"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.
Free to start. No card required.
Get details for a collection. It is categorised as a Read tool in the PocketBase MCP Server MCP Server, which means it retrieves data without modifying state.
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.
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 PocketBase MCP Server MCP server (mrwyndham/pocketbase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PocketBase MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
24 PocketBase MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.