Execute a SQL query against a SQLite database and return the results. Modes: -
AI agents invoke db_query to trigger actions in MCP Toolkit 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 arbitrary SQL, which can include SELECT (Read), INSERT/UPDATE (Write), DELETE/DROP (Destructive), or other dangerous statements. Since the description does not restrict query types and explicitly says 'execute a SQL query,' the most severe applicable category is Execute (potentially Destructive).
From the tool's definition "Execute a SQL query against a SQLite database" — the tool runs arbitrary SQL statements against a database.
Attacks that exploit this kind of access
Execute a SQL query against a SQLite database and return the results. Modes: -. It is categorised as a Execute tool in the MCP Toolkit Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Toolkit Server MCP server in PolicyLayer and add a rule for db_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 MCP Toolkit Server. Nothing to install.
db_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 db_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 db_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.
db_query is provided by the MCP Toolkit Server MCP server (vyshnavi-nandyala/mcp-toolkit-server). 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 →