Route user query to appropriate tools across all servers. Use this when you need to find specific tools that can address the user
AI agents call route-tools to retrieve information from MCP Server Copilot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs discovery and routing of queries to appropriate tools—it is fundamentally a read operation that searches and returns information about available tools. It does not execute tools, modify data, delete resources, or commit financial transactions. While it facilitates access to other tools, the tool itself only reads/queries metadata about available tools.
From the tool's definition Tool name 'route-tools' and description 'Route user query to appropriate tools across all servers. Use this when you need to find specific tools that can address the user' indicate a query/routing function that retrieves tool information without modifying…
Documented attack patterns abuse exactly the kind of access route-tools gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server Copilot, and nothing reaches the server without passing your rules. This is the rule we recommend for route-tools:
{
"version": "1",
"default": "deny",
"tools": {
"route-tools": {}
}
}route-tools is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Route user query to appropriate tools across all servers. Use this when you need to find specific tools that can address the user. It is categorised as a Read tool in the MCP Server Copilot MCP Server, which means it retrieves data without modifying state.
Register the MCP Server Copilot MCP server in PolicyLayer and add a rule for route-tools: 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 Copilot. Nothing to install.
route-tools is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the route-tools 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-tools. 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-tools is provided by the MCP Server Copilot MCP server (tshu-w/mcp-copilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server Copilot, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 MCP Server Copilot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.