This record as markdown: /tools/io-github-kivanccakmak-yaver/cloud-logs.md
What cloud_logs does on Yaver
AI agents call cloud_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 |
|---|---|---|---|
app | string | — | App name |
lines | integer | — | Number of lines (default: 100) |
Parameters from the server's own tool schema.
Why cloud_logs is rated Low
This tool retrieves log data for inspection and monitoring purposes. It is a read-only operation with no side effects, no code execution, and no data modification. While logs may contain sensitive information (which could raise severity), the tool itself performs only retrieval. Severity is low because log access on a developer's own deployed app is expected in a local dev environment context.
From the tool's definition Tool name 'cloud_logs' and description 'Get logs from a cloud-deployed app' indicate retrieval of existing log data with no modification or destructive capability.
Attacks that exploit this kind of access
The rule that runs cloud_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 cloud_logs, this is the rule to start with:
cloud_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 cloud_logs call is checked against it from then on.
Questions about cloud_logs
Get logs from a cloud-deployed app. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
cloud_logs accepts 2 parameters: app, 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 cloud_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.
cloud_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 cloud_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 cloud_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.
cloud_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