Execute a SPASQL query and return results.
AI agents invoke spasql_query 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.
SPASQL (SPARQL inside SQL) queries are executed against a database. The tool runs arbitrary query statements which could include data modification operations (INSERT, UPDATE, DELETE) depending on what the user submits. Since it executes arbitrary queries rather than being a read-only SELECT, this falls under Execute.
From the tool's definition Execute a SPASQL query and return results
Documented attack patterns abuse exactly the kind of access spasql_query 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 spasql_query:
{
"version": "1",
"default": "deny",
"tools": {
"spasql_query": {
"limits": [
{
"counter": "spasql_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} spasql_query 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 SPASQL query and return results. 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 spasql_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 Odbc. Nothing to install.
spasql_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 spasql_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 spasql_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.
spasql_query 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.