Execute a SPASQL query and return results.
AI agents invoke spasql_query to trigger actions in OpenLink MCP Server for 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.
Executing arbitrary SPASQL queries can perform reads but also potentially trigger writes, updates, or destructive operations depending on the query content. The 'execute' verb and query execution nature place this in the Execute category.
From the tool's definition 'Execute a SPASQL query and return results' — the tool actively executes a query (SPASQL, a hybrid SPARQL/SQL language) against an ODBC-accessible database.
Attacks that exploit this kind of access
Execute a SPASQL query and return results. It is categorised as a Execute tool in the OpenLink MCP Server for ODBC MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OpenLink MCP Server for 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 OpenLink MCP Server for 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 OpenLink MCP Server for ODBC MCP server (pvsmark/pvs-odbc-mcp). 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 →