Run a SQL query against Microsoft SQL Server
AI agents invoke run_query to trigger actions in Amazon MQ MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes SQL queries, which can trigger arbitrary database operations. While the description doesn't explicitly list destructive operations (DROP, DELETE, etc.), SQL queries can include such commands depending on what the AI agent constructs. The execution capability, combined with database access, poses a high severity risk—the agent could modify, exfiltrate, or corrupt data.
From the tool's definition Tool name 'run_query' and description 'Run a SQL query against Microsoft SQL Server' explicitly indicates execution of arbitrary SQL commands against a database.
Attacks that exploit this kind of access
Run a SQL query against Microsoft SQL Server. It is categorised as a Execute tool in the Amazon MQ MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for run_query: 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.
run_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_query 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 run_query. 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.
run_query 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.