list_databases
AI agents call list_databases 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 tool name clearly denotes a retrieval action (list) that queries existing databases without creating, modifying, deleting, or executing operations. In the context of an Amazon MQ management server, listing databases would retrieve metadata about broker resources, which is a read-only operation with minimal blast radius if invoked inappropriately.
From the tool's definition Tool name 'list_databases' indicates a listing/querying operation with no modification capability. The description is empty, but the verb 'list' is a standard Read operation pattern.
Attacks that exploit this kind of access
list_databases. 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 list_databases: 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.
list_databases 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_databases 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_databases. 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_databases 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.