Get Mender audit logs with optional filtering
AI agents call get_audit_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 and queries audit log data without side effects. It is a read-only operation consistent with the server's stated read-only access model. Audit logs themselves are historical records, and retrieving them poses minimal risk even if accessed by an AI agent, as no state is modified.
From the tool's definition Tool name 'get_audit_logs' and description 'Get Mender audit logs with optional filtering' indicate retrieval of existing audit log data.
Attacks that exploit this kind of access
Get Mender audit logs 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 get_audit_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_audit_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_audit_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_audit_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_audit_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 →