Get the details of a specific release
AI agents call get_release_status 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 release details without modifying or deleting data. It is a simple query operation that returns information about a release in the Mender IoT platform. The read-only nature confirmed by the server description and the pattern of sibling tools establishes this as a Read operation with low severity—exposing release details poses minimal security risk even with unrestricted use by an AI agent.
From the tool's definition Tool name 'get_release_status' and description 'Get the details of a specific release' indicate retrieval of release information.
Attacks that exploit this kind of access
Get the details of a specific release. 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_release_status: 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_release_status 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_release_status 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_release_status. 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_release_status 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 →