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 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 data from a PocketBase collection without creating, modifying, deleting, executing code, or committing financial transactions. The filtering, sorting, and pagination are all read-only query parameters that do not alter data. There are no side effects beyond data retrieval.
From the tool's definition Tool name is 'list_records' and description states it 'List records from a PocketBase collection with optional filtering, sorting, and pagination.
Attacks that exploit this kind of access
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 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 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 Ssakone Pocketbase. 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 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 →