List records from a PocketBase collection with optional filtering, sorting, and pagination. Returns records with pagination metadata.
AI agents call list_records 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 performs a read-only query operation that retrieves and returns existing data from a collection. It has no side effects on data state (no creation, modification, or deletion). The pagination, filtering, and sorting parameters are all part of standard query refinement, not operational changes.
From the tool's definition Tool description states 'List records from a PocketBase collection' with 'filtering, sorting, and pagination' and 'Returns records' — purely a retrieval operation with no modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access list_records 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_records:
{
"version": "1",
"default": "deny",
"tools": {
"list_records": {}
}
}list_records 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.
List records from a PocketBase collection with optional filtering, sorting, and pagination. Returns records with pagination metadata. 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 list_records: 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.
list_records 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_records 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_records. 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_records 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.
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.