This record as markdown: /tools/io-github-kivanccakmak-yaver/services-logs.md
What services_logs does on Yaver
AI agents call services_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 |
|---|---|---|---|
name | string | Yes | Service name |
lines | integer | — | Number of lines (default: 50) |
Parameters from the server's own tool schema.
Why services_logs is rated Low
This tool retrieves and queries log data from a running service. It has no side effects—it does not modify, delete, execute, or trigger operations. Log retrieval is a standard Read category operation, with low severity since logs typically contain non-sensitive operational data in development environments, though context-dependent information exposure is possible.
From the tool's definition Tool name 'services_logs' and description 'Tail logs from a service' indicate log retrieval with no modification, deletion, or execution capability. Tailing logs is a read-only diagnostic operation.
Attacks that exploit this kind of access
The rule that runs services_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 services_logs, this is the rule to start with:
services_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 services_logs call is checked against it from then on.
Questions about services_logs
Tail logs from a service. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
services_logs accepts 2 parameters: name, lines. Required: name. 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 services_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.
services_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 services_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 services_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.
services_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