This record as markdown: /tools/io-github-kivanccakmak-yaver/data-browse.md
What data_browse does on Yaver
AI agents call data_browse 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 |
|---|---|---|---|
limit | number | — | |
table | string | Yes | |
cursor | string | — | |
directory | string | — |
Parameters from the server's own tool schema.
Why data_browse is rated Low
The tool retrieves and navigates data with pagination but does not create, modify, delete, or execute operations. This is a pure read/query action. Severity is low because browsing data typically has minimal blast radius unless the backend contains highly sensitive information, but the tool itself imposes no destructive or operational risk.
From the tool's definition Tool description explicitly states 'Browse rows/documents with pagination' — a retrieval operation with no modification capability indicated. No write, delete, execute, or financial operations are mentioned.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs data_browse 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 data_browse, this is the rule to start with:
data_browse 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 data_browse call is checked against it from then on.
Questions about data_browse
Browse rows/documents with pagination across any backend. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
data_browse accepts 4 parameters: limit, table, cursor, directory. Required: table. 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 data_browse: 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.
data_browse 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 data_browse 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 data_browse. 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.
data_browse 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