yaver_clear_logs

Clear the agent log file.

SERVERYaver SOURCEyaver-cli

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-clear-logs.md

WHAT IT DOES

What yaver_clear_logs does on Yaver

AI agents call yaver_clear_logs to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why yaver_clear_logs is rated Critical

Clearing a log file permanently destroys all log data it contained. This cannot be undone, making it a Destructive action. Severity is medium because logs are operational/diagnostic data rather than primary application data, but loss of logs can impair debugging, auditing, and incident response.

From the tool's definition 'Clear the agent log file' — clearing/wiping a log file is an irreversible deletion of its contents

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs yaver_clear_logs 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 yaver_clear_logs, this is the rule to start with:

yaver_clear_logs Hidden

yaver_clear_logs is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "yaver_clear_logs"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every yaver_clear_logs call is checked against it from then on.

FAQ

Questions about yaver_clear_logs

What does the yaver_clear_logs tool do? +

Clear the agent log file. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on yaver_clear_logs? +

Register the Yaver MCP server in PolicyLayer and add a rule for yaver_clear_logs: 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.

What risk level is yaver_clear_logs? +

yaver_clear_logs is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit yaver_clear_logs? +

Yes. Add a rate_limit block to the yaver_clear_logs 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.

How do I block yaver_clear_logs completely? +

Set action: deny in the PolicyLayer policy for yaver_clear_logs. 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.

What MCP server provides yaver_clear_logs? +

yaver_clear_logs 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → Critical-risk tools on this server →

Across the catalogue

clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP →clear_spam_box on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →