session-sql
AI agents invoke session-sql 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.
The name 'session-sql' strongly implies executing SQL queries within a session. Given the server context (Amazon MQ broker management), this likely involves running SQL-like commands against message broker resources. The description is empty, which lowers confidence, but the name pattern suggests Execute category.
From the tool's definition Tool name 'session-sql' suggests SQL execution within a session context on an Amazon MQ broker management server
Attacks that exploit this kind of access
session-sql. 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 session-sql: 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.
session-sql 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 session-sql 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 session-sql. 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.
session-sql 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.