convex_install_helper
Write convex/yaver_admin.ts helper functions into a project so the Yaver dashboard can introspect it.
This record as markdown: /tools/io-github-kivanccakmak-yaver/convex-install-helper.md
What convex_install_helper does on Yaver
AI agents use convex_install_helper to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
directory | string | Yes |
Parameters from the server's own tool schema.
Why convex_install_helper is rated Medium
This tool creates or modifies files in a project, which is reversible and fits the Write category. While it modifies project code (not user data), the modification is intentional and can be reverted.
From the tool's definition The tool 'Write convex/yaver_admin.ts helper functions into a project' explicitly performs file creation/modification (write operation) into the project directory.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs convex_install_helper 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_install_helper, this is the rule to start with:
convex_install_helper stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_install_helper call is checked against it from then on.
Questions about convex_install_helper
Write convex/yaver_admin.ts helper functions into a project so the Yaver dashboard can introspect it. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
convex_install_helper accepts 1 parameter: directory. Required: 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_install_helper: 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_install_helper is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the convex_install_helper 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_install_helper. 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_install_helper 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