route_query
AI agents invoke route_query to trigger actions in MCP Server Proto-OKN. 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 server is designed for querying SPARQL endpoints. The tool name 'route_query' suggests it routes or dispatches queries to appropriate SPARQL endpoints, which is an Execute-level action (running queries against external systems). Sibling tools like 'multi_graph_query' and 'get_query_template' reinforce this pattern. However, the empty description lowers confidence significantly.
From the tool's definition Tool name 'route_query' on a server specialized for querying SPARQL endpoints; description is empty/uninformative.
Attacks that exploit this kind of access
route_query. It is categorised as a Execute tool in the MCP Server Proto-OKN MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Server Proto-OKN MCP server in PolicyLayer and add a rule for route_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 Server Proto-OKN. Nothing to install.
route_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 route_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 route_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.
route_query is provided by the MCP Server Proto-OKN MCP server (sbl-sdsc/mcp-proto-okn). 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 →