Check if a connection has been established
AI agents call is_database_connected 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.
This tool queries the state of a database connection but performs no modifications, executions, or destructive actions. It is a passive diagnostic check that retrieves information about connection status, fitting the Read category. The low severity reflects minimal blast radius—misuse would at worst provide misleading status information without affecting system state or data.
From the tool's definition Tool name 'is_database_connected' and description 'Check if a connection has been established' indicate a read-only status check operation with no side effects.
Attacks that exploit this kind of access
Check if a connection has been established. 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 is_database_connected: 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.
is_database_connected 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 is_database_connected 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 is_database_connected. 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.
is_database_connected 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.