List releases with optional filtering
AI agents call list_releases 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 and queries release data with optional filters, which is a classic read operation with no side effects. The server's explicit 'read-only access' designation and the tool's sibling tools (all prefixed with 'get_' or 'list_') confirm this is a data retrieval mechanism. Low severity reflects that querying release information poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'list_releases' and description 'List releases with optional filtering' indicate a retrieval operation. Server description explicitly states 'read-only access' to releases among other resources.
Attacks that exploit this kind of access
List releases with optional filtering. 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 list_releases: 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.
list_releases 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 list_releases 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 list_releases. 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.
list_releases 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 →