This record as markdown: /tools/io-github-kivanccakmak-yaver/convex-run.md
What convex_run does on Yaver
AI agents invoke convex_run 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 | Function path (e.g. tasks:list) |
directory | string | — |
Parameters from the server's own tool schema.
Why convex_run is rated High
This tool executes code (Convex functions) whose effects depend on the specific function argument passed. While the description doesn't explicitly state whether destructive operations are possible, running arbitrary backend functions via an MCP tool creates substantial risk for unintended side effects, data modification, or external API calls.
From the tool's definition Tool name is 'convex_run' and description states 'Run a Convex function.' The verb 'run' combined with execution of arbitrary functions indicates arbitrary code execution.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs convex_run 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_run, this is the rule to start with:
convex_run 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_run call is checked against it from then on.
Questions about convex_run
Run a Convex function. 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_run 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_run: 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_run 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_run 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_run. 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_run 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