Récupère un record spécifique d\
AI agents call pocketbase-fetch-record 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.
This tool queries and retrieves a specific record from the PocketBase database. It performs a read-only operation with no side effects—no data is created, modified, deleted, or executed. The confidence is high despite the truncated description because the tool name and opening verb clearly indicate a fetch/retrieval operation.
From the tool's definition Tool name 'pocketbase-fetch-record' and description beginning 'Récupère un record spécifique d' (French: 'Retrieves a specific record') indicate data retrieval without modification.
Attacks that exploit this kind of access
Récupère un record spécifique d\. 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 pocketbase-fetch-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 PocketBase MCP Server. Nothing to install.
pocketbase-fetch-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 pocketbase-fetch-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 pocketbase-fetch-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.
pocketbase-fetch-record is provided by the PocketBase MCP Server MCP server (step-by-step-technology/pocketbase-mcp). 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 →