run_odin_query
AI agents invoke run_odin_query to trigger actions in SB OGC MCP. 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 'run_' prefix combined with 'query' indicates code/operation execution rather than simple data retrieval. While the description is empty (reducing confidence slightly), the tool's position among other 'run_' tools that execute complex analyses on mobility datasets confirms Execute category.
From the tool's definition Tool name 'run_odin_query' with 'run_' prefix indicates execution of a query operation. The description is empty, preventing full verification, but context shows this server provides access to Dutch mobility data via OGC API.
Attacks that exploit this kind of access
run_odin_query. It is categorised as a Execute tool in the SB OGC MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SB OGC MCP server in PolicyLayer and add a rule for run_odin_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 SB OGC MCP. Nothing to install.
run_odin_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 run_odin_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 run_odin_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.
run_odin_query is provided by the SB OGC MCP server (studio-bereikbaar/sb-ogc-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 →