Execute a SQL query and return results in MD format.
AI agents invoke query_database_md to trigger actions in Mcp Odbc. 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 queries against a database. While it may be intended for SELECT statements, 'execute a SQL query' implies no restriction on query type, meaning it could run DDL (DROP, CREATE), DML (INSERT, UPDATE, DELETE), or other destructive/modifying statements. The blast radius is critical given it can touch any ODBC-accessible DBMS.
From the tool's definition "Execute a SQL query" — runs arbitrary SQL against an ODBC-connected DBMS and returns results in Markdown format.
Documented attack patterns abuse exactly the kind of access query_database_md gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Odbc, and nothing reaches the server without passing your rules. This is the rule we recommend for query_database_md:
{
"version": "1",
"default": "deny",
"tools": {
"query_database_md": {
"limits": [
{
"counter": "query_database_md_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} query_database_md stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute a SQL query and return results in MD format. It is categorised as a Execute tool in the Mcp Odbc MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Odbc MCP server in PolicyLayer and add a rule for query_database_md: 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 Odbc. Nothing to install.
query_database_md 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 query_database_md 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 query_database_md. 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.
query_database_md is provided by the Mcp Odbc MCP server (openlinksoftware/mcp-odbc-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Odbc, 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.
15 Mcp Odbc tools catalogued and risk-classified — across an index of 43,000+ MCP servers.