convex_tables
List tables in the local Convex backend (requires yaver_admin.ts helper).
This record as markdown: /tools/io-github-kivanccakmak-yaver/convex-tables.md
What convex_tables does on Yaver
AI agents call convex_tables 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 |
|---|---|---|---|
directory | string | — |
Parameters from the server's own tool schema.
Why convex_tables is rated Low
This tool performs a read-only operation—listing available tables in a backend database. It retrieves metadata about the data structure without creating, modifying, deleting, or executing arbitrary code. The requirement for 'yaver_admin.ts helper' suggests authentication/authorization but does not change the fundamental read-only nature of the action.
From the tool's definition Tool name 'convex_tables' and description 'List tables in the local Convex backend' indicates a query/retrieval operation with no modification or deletion of data.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs convex_tables 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_tables, this is the rule to start with:
convex_tables 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_tables call is checked against it from then on.
Questions about convex_tables
List tables in the local Convex backend (requires yaver_admin.ts helper). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
convex_tables accepts 1 parameter: directory. 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_tables: 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_tables 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_tables 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_tables. 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_tables 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