This record as markdown: /tools/io-github-kivanccakmak-yaver/convex-mutate.md
What convex_mutate does on Yaver
AI agents invoke convex_mutate 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 | — | |
function | string | Yes | |
directory | string | — |
Parameters from the server's own tool schema.
Why convex_mutate is rated High
This tool executes mutations on a Convex backend via an admin API. Mutations are state-modifying operations whose effects depend entirely on the mutation name and arguments provided by the caller. While mutations are not inherently destructive (they don't irreversibly delete data), they perform execute-category operations by triggering external backend code with side effects.
From the tool's definition Tool description states 'Run a Convex mutation via admin HTTP API'. The word 'Run' combined with 'mutation' (a command that modifies state in backend systems) indicates execution of external operations.
Risk signalsAccepts file system path (directory) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs convex_mutate 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_mutate, this is the rule to start with:
convex_mutate 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_mutate call is checked against it from then on.
Questions about convex_mutate
Run a Convex mutation via admin HTTP API. 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_mutate 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_mutate: 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_mutate 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_mutate 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_mutate. 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_mutate 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