This record as markdown: /tools/io-github-kivanccakmak-yaver/auth-log.md
What auth_log does on Yaver
AI agents call auth_log 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 | — |
Parameters from the server's own tool schema.
Why auth_log is rated Low
This tool retrieves and displays authentication and SSH log entries for inspection purposes. It has no side effects—it queries existing logs without creating, modifying, deleting, or executing anything. This is a straightforward read operation with minimal risk, as logs are typically informational data.
From the tool's definition Tool name 'auth_log' and description 'Show authentication/SSH logs' indicate retrieval and display of existing log data with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs auth_log 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 auth_log, this is the rule to start with:
auth_log 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 auth_log call is checked against it from then on.
Questions about auth_log
Show authentication/SSH logs. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
auth_log 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 auth_log: 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.
auth_log 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 auth_log 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 auth_log. 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.
auth_log 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