get_sql_query_mcp
AI agents invoke get_sql_query_mcp to trigger actions in ADT 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 tool name 'get_sql_query_mcp' suggests it executes SQL queries against a SAP ABAP system. SQL execution tools carry high risk as they may run arbitrary queries including destructive ones. However, the 'get_' prefix may imply read-only SELECT queries. The empty description reduces confidence significantly.
From the tool's definition Tool name contains 'sql_query' suggesting it runs SQL queries; description is empty and uninformative.
Attacks that exploit this kind of access
get_sql_query_mcp. It is categorised as a Execute tool in the ADT MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ADT MCP Server MCP server in PolicyLayer and add a rule for get_sql_query_mcp: 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 ADT MCP Server. Nothing to install.
get_sql_query_mcp 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 get_sql_query_mcp 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 get_sql_query_mcp. 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.
get_sql_query_mcp is provided by the ADT MCP Server MCP server (yahornovik/mcp-adt). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →