audit_slos
AI agents call audit_slos to retrieve information from Amazon MQ MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'audit' prefix typically indicates inspection or review of existing data without modification. SLO auditing is a read-only operation that checks metrics and compliance status. However, confidence is reduced to 0.6 due to missing tool description, which prevents full verification of actual behavior. If this tool instead modifies audit logs or SLO configurations, severity could be higher.
From the tool's definition Tool name 'audit_slos' suggests querying or reviewing Service Level Objectives (SLOs) for compliance/monitoring purposes. No description provided.
Attacks that exploit this kind of access
audit_slos. It is categorised as a Read tool in the Amazon MQ MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for audit_slos: 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 Amazon MQ MCP Server. Nothing to install.
audit_slos 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 audit_slos 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 audit_slos. 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.
audit_slos is provided by the Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.