This record as markdown: /tools/io-github-kivanccakmak-yaver/convex-browse.md
What convex_browse does on Yaver
AI agents call convex_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 convex_browse is rated Low
Browsing documents is a query operation that retrieves data for inspection without creating, modifying, deleting, or executing operations. This is a standard Read category tool with minimal blast radius if misused by an AI agent—it can only access information already stored in the Convex backend.
From the tool's definition Tool name 'convex_browse' and description 'Browse documents in a Convex table' indicate data retrieval without modification. The verb 'browse' implies read-only access to existing data.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs convex_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 convex_browse, this is the rule to start with:
convex_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 convex_browse call is checked against it from then on.
Questions about convex_browse
Browse documents in a Convex table. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
convex_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 convex_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.
convex_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 convex_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 convex_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.
convex_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