Execute a read-only SQL SELECT query against the IBM DB2i database. Only SELECT statements are allowed for security. Results are limited by default to prevent large result sets.
AI agents call execute_query to retrieve information from Db2i without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool explicitly restricts execution to SELECT statements and is described as read-only, placing it firmly in the Read category. Medium severity because even read-only SQL queries can expose sensitive data across the entire database if misused, and the enforcement of the SELECT-only restriction is described in text rather than verified technically.
From the tool's definition Execute a read-only SQL SELECT query... Only SELECT statements are allowed for security.
Documented attack patterns abuse exactly the kind of access execute_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Db2i, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_query:
{
"version": "1",
"default": "deny",
"tools": {
"execute_query": {}
}
}execute_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute a read-only SQL SELECT query against the IBM DB2i database. Only SELECT statements are allowed for security. Results are limited by default to prevent large result sets. It is categorised as a Read tool in the Db2i MCP Server, which means it retrieves data without modifying state.
Register the Db2i MCP server in PolicyLayer and add a rule for execute_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 Db2i. Nothing to install.
execute_query 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 execute_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 execute_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.
execute_query is provided by the Db2i MCP server (strom-capital/mcp-server-db2i). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Db2i, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Db2i tools catalogued and risk-classified — across an index of 43,000+ MCP servers.