resources_runtime_logs
Read resources.runtime-logs through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/resources-runtime-logs.md
What resources_runtime_logs does on Appaloft
AI agents call resources_runtime_logs to retrieve information from Appaloft 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 |
|---|---|---|---|
since | string | — | |
cursor | string | — | |
follow | object | — | |
tailLines | integer | — | |
resourceId | string | — | |
serviceName | string | — | |
deploymentId | string | — | |
previewEnvironmentId | string | — |
Parameters from the server's own tool schema.
Why resources_runtime_logs is rated Low
This tool retrieves runtime logs for inspection and analysis. Logs are informational data that can be queried but not modified through this tool. Runtime logs may contain sensitive information (moderate data exposure risk), but the tool itself performs a read-only operation.
From the tool's definition Tool name contains 'logs' and description explicitly states 'Read resources.runtime-logs'. The verb 'Read' and retrieval of runtime logs indicate a data query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs resources_runtime_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For resources_runtime_logs, this is the rule to start with:
resources_runtime_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 Appaloft, apply this rule, and every resources_runtime_logs call is checked against it from then on.
Questions about resources_runtime_logs
Read resources.runtime-logs through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Read tool in the Appaloft MCP Server, which means it retrieves data without modifying state.
resources_runtime_logs accepts 8 parameters: since, cursor, follow, tailLines, resourceId, serviceName, deploymentId, previewEnvironmentId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for resources_runtime_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 Appaloft. Nothing to install.
resources_runtime_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 resources_runtime_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 resources_runtime_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.
resources_runtime_logs is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
This server
Across the catalogue