This record as markdown: /tools/io-github-kivanccakmak-yaver/backend-records.md
What backend_records does on Yaver
AI agents call backend_records to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sort | string | — | |
limit | integer | — | |
filter | string | — | |
collection | string | Yes |
Parameters from the server's own tool schema.
Why backend_records is rated Low
The tool performs data retrieval from a database (PocketBase). While it is read-only and thus lower risk than write/execute/destructive operations, the severity is elevated to 'medium' because: (1) it may expose sensitive application data, customer information, or credentials depending on what records are stored; (2) in a local dev context with mobile pairing, access controls may be relaxed; (3) an AI agent with…
From the tool's definition Tool name and description state 'Query PocketBase records' — a read-only operation that retrieves data without modification.
Attacks that exploit this kind of access
The rule that runs backend_records safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For backend_records, this is the rule to start with:
backend_records is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every backend_records call is checked against it from then on.
Questions about backend_records
Query PocketBase records. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
backend_records accepts 4 parameters: sort, limit, filter, collection. Required: collection. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for backend_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 Yaver. Nothing to install.
backend_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 backend_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 backend_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.
backend_records is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue