Tool to use the Virtuoso AI support function
AI agents invoke virtuoso_support_ai 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.
The tool name references 'Virtuoso' (a database engine) and 'AI support function', suggesting it triggers some AI or database operation. Given the server context (ODBC, SQL, SPARQL execution) and that it's an 'AI support function' rather than a simple read, it likely executes queries or invokes server-side AI capabilities.
From the tool's definition 'Virtuoso AI support function' - description is vague and uninformative about specific actions
Attacks that exploit this kind of access
Tool to use the Virtuoso AI support function. 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 virtuoso_support_ai: 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.
virtuoso_support_ai 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 virtuoso_support_ai 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 virtuoso_support_ai. 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.
virtuoso_support_ai 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 →