Get recent log lines for a Docker container.
AI agents call get_container_logs to retrieve information from Synology MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries existing log data from a Docker container without modifying, deleting, or executing any operations. Log retrieval is a read-only action that does not change system state. Severity is low because logs typically contain operational information but not sensitive credentials in a properly configured system, and the blast radius of misuse is limited to information disclosure.
From the tool's definition Tool name is 'get_container_logs' and description states 'Get recent log lines for a Docker container' — this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get recent log lines for a Docker container. It is categorised as a Read tool in the Synology MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Synology MCP Server MCP server in PolicyLayer and add a rule for get_container_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 Synology MCP Server. Nothing to install.
get_container_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 get_container_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 get_container_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.
get_container_logs is provided by the Synology MCP Server MCP server (rafalr100/synology-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →