Get deployment logs for all devices in a deployment
AI agents call get_deployment_logs to retrieve information from Mender MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical deployment log information without side effects. It queries existing data for monitoring and analysis purposes, consistent with read-only access patterns. The blast radius of misuse is minimal—an attacker could only gain visibility into deployment history, not modify systems or cause harm. Low severity is appropriate for information disclosure in a monitoring context.
From the tool's definition Tool name 'get_deployment_logs' and description 'Get deployment logs for all devices in a deployment' indicate retrieval of existing log data.
Attacks that exploit this kind of access
Get deployment logs for all devices in a deployment. It is categorised as a Read tool in the Mender MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mender MCP Server MCP server in PolicyLayer and add a rule for get_deployment_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 Mender MCP Server. Nothing to install.
get_deployment_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_deployment_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_deployment_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_deployment_logs is provided by the Mender MCP Server MCP server (pasinskim/mender-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 →