This record as markdown: /tools/io-github-kivanccakmak-yaver/convex-query.md
What convex_query does on Yaver
AI agents invoke convex_query to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
args | string | — | JSON args |
function | string | Yes | |
directory | string | — |
Parameters from the server's own tool schema.
Why convex_query is rated High
Although named 'query' (suggesting read-only), it runs operations via an admin HTTP API which could execute arbitrary Convex query functions with significant permissions. Admin APIs typically have elevated privileges and the query could trigger side effects, access sensitive data, or run complex logic. The 'admin' qualifier raises severity above a typical read operation.
From the tool's definition "Run a Convex query via admin HTTP API" — executes queries through an admin API endpoint
Risk signalsAccepts file system path (directory) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs convex_query 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_query, this is the rule to start with:
convex_query stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_query call is checked against it from then on.
Questions about convex_query
Run a Convex query via admin HTTP API (no CLI). It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
convex_query accepts 3 parameters: args, function, directory. Required: function. 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_query: 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_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the convex_query 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_query. 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_query 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.
Across the catalogue