esm_kafka_diagnosis
AI agents call esm_kafka_diagnosis 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.
With an empty description, confidence is moderate. The tool name suggests diagnosis/monitoring (Read category), but lack of detail prevents higher confidence. In Amazon MQ context, diagnostic tools typically query broker logs, metrics, and state—side-effect-free operations.
From the tool's definition Tool name 'esm_kafka_diagnosis' suggests diagnostic/monitoring functionality typical of read-only operations. The 'diagnosis' suffix commonly refers to analysis and querying of system state without modification.
Attacks that exploit this kind of access
esm_kafka_diagnosis. 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 esm_kafka_diagnosis: 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.
esm_kafka_diagnosis 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 esm_kafka_diagnosis 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 esm_kafka_diagnosis. 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.
esm_kafka_diagnosis 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.