Get a single record by ID from a PocketBase collection. Returns the full record with all fields.
AI agents call get_record 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 side effects. It queries and returns information based on the provided record ID, matching the Read category definition of retrieving or querying data with no side effects. The low severity reflects that data retrieval alone presents minimal risk unless the data itself is highly sensitive, but the tool mechanism itself is not dangerous.
From the tool's definition Tool description explicitly states 'Get a single record by ID' and 'Returns the full record with all fields' — retrieval operations with no modification or deletion.
Attacks that exploit this kind of access
Get a single record by ID from a PocketBase collection. Returns the full record with all fields. 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_record: 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_record 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_record 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_record. 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_record 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 →