Use the SPARQL AI Agent function
AI agents invoke podbc_sparql_func to trigger actions in MCP PyODBC 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.
The tool invokes an AI Agent function through SPARQL, which goes beyond simple data retrieval. It executes external operations whose effects depend on the arguments passed to the AI agent. The blast radius is high because AI agent functions can perform arbitrary actions including data modification, queries, or other side effects depending on how the agent is configured.
From the tool's definition 'Use the SPARQL AI Agent function' — triggers an AI agent function via SPARQL, implying execution of dynamic operations against a database
Attacks that exploit this kind of access
Use the SPARQL AI Agent function. It is categorised as a Execute tool in the MCP PyODBC Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP PyODBC Server MCP server in PolicyLayer and add a rule for podbc_sparql_func: 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 PyODBC Server. Nothing to install.
podbc_sparql_func 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 podbc_sparql_func 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 podbc_sparql_func. 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.
podbc_sparql_func is provided by the MCP PyODBC Server MCP server (openlinksoftware/mcp-pyodbc-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 →