Get deployment logs for a specific device in a deployment
AI agents call get_deployment_device_log 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 data for audit and monitoring purposes. It performs a query operation with no capability to modify, delete, or execute actions. The read-only nature is reinforced by the server's stated design. While deployment logs could theoretically contain sensitive information, the classification is based on the operation type (retrieval), not the sensitivity of data returned.
From the tool's definition Tool name 'get_deployment_device_log' uses the 'get' verb indicating retrieval. Description states 'Get deployment logs for a specific device in a deployment'.
Attacks that exploit this kind of access
Get deployment logs for a specific device 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_device_log: 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_device_log 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_device_log 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_device_log. 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_device_log 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 →