This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-logs.md
What yaver_logs does on Yaver
AI agents call yaver_logs to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
lines | integer | — | Number of log lines to return (default 50, max 500) |
Parameters from the server's own tool schema.
Why yaver_logs is rated Low
This tool queries and retrieves historical log data. It is a straightforward read operation that does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal — an agent could only view existing logs without affecting system state or data integrity.
From the tool's definition Tool description explicitly states 'View the last N lines of the agent log file' — a read-only retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs yaver_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_logs, this is the rule to start with:
yaver_logs is read-only, so it stays allowed. 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 yaver_logs call is checked against it from then on.
Questions about yaver_logs
View the last N lines of the agent log file. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
yaver_logs accepts 1 parameter: lines. 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 yaver_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.
yaver_logs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the yaver_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.
Set action: deny in the PolicyLayer policy for yaver_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.
yaver_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.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue