This record as markdown: /tools/io-github-kivanccakmak-yaver/make-run.md
What make_run does on Yaver
AI agents invoke make_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 |
|---|---|---|---|
target | string | — | |
directory | string | — |
Parameters from the server's own tool schema.
Why make_run is rated High
The tool triggers execution of Makefile targets, which are arbitrary code/commands and not confined to read-only operations. In a mobile dev environment (Yaver for Claude Code/Codex), Make targets commonly invoke compilers, deploy scripts, or system commands. The outcome depends entirely on what targets are defined in the Makefile, making this an Execute-category tool.
From the tool's definition Tool name 'make_run' and description 'Run a Make target' indicate execution of arbitrary build targets via Make, which can execute shell commands and external operations.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs make_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 make_run, this is the rule to start with:
make_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 make_run call is checked against it from then on.
Questions about make_run
Run a Make target. 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.
make_run accepts 2 parameters: target, 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 make_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.
make_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 make_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 make_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.
make_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