This record as markdown: /tools/io-github-kivanccakmak-yaver/make-clean.md
What make_clean does on Yaver
AI agents invoke make_clean 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 |
|---|---|---|---|
directory | string | — |
Parameters from the server's own tool schema.
Why make_clean is rated High
The tool triggers execution of an external command ('make clean') whose effects depend on the project's build configuration and Makefile contents. While 'clean' targets typically remove build artifacts (reversible), the tool fundamentally executes arbitrary build system commands, which qualifies as Execute category.
From the tool's definition Tool name 'make_clean' and description 'Run make clean' indicate execution of a make system command that cleans build artifacts. This is a command execution operation.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs make_clean 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_clean, this is the rule to start with:
make_clean 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_clean call is checked against it from then on.
Questions about make_clean
Run make clean. 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_clean accepts 1 parameter: 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_clean: 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_clean 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_clean 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_clean. 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_clean 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