route_query
A execute tool on the 1c Mcp Rag Search MCP server.
This record as markdown: /tools/1c-mcp-rag-search/route-query.md
What route_query does on 1c Mcp Rag Search
AI agents invoke route_query to trigger actions in 1c Mcp Rag Search. 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.
Why route_query is rated High
The tool description is empty, which lowers confidence significantly. However, based on the server's purpose and sibling tools, 'route_query' likely dispatches queries to other MCP tools and planners — effectively triggering external operations on behalf of the caller. This is an Execute-level concern because routing can invoke arbitrary downstream tools with unpredictable side effects.
From the tool's definition Tool name 'route_query' on a server described as routing 'natural language queries to appropriate MCP tools and planners' with 'multi-intent detection, task planning, and strict role-based filtering to prevent misexecution or unauthorized access.'
Attacks that exploit this kind of access
The rule that runs route_query safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1c Mcp Rag Search, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For route_query, this is the rule to start with:
route_query stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 1c Mcp Rag Search, apply this rule, and every route_query call is checked against it from then on.
Questions about route_query
route_query is a execute tool on the 1c Mcp Rag Search MCP server. It is categorised as a Execute tool in the 1c Mcp Rag Search MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 1c Mcp Rag Search 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 1c Mcp Rag Search. 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 1c Mcp Rag Search MCP server (Smaturus/1c-mcp-rag-search). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1c Mcp Rag Search, and thousands of servers like it.
Across the catalogue