route_tool

What route_tool does on Jshookmcp

AI agents invoke route_tool to trigger actions in Jshookmcp. 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_tool is rated High

Although the description suggests it may only return recommendations, a 'tool router' on a server with exploit-building and browser automation siblings likely orchestrates execution of those tools. The blast radius is high because misuse could chain into destructive or exploit-related operations. Confidence is moderate because the description is ambiguous about whether it executes or merely recommends.

From the tool's definition 'One-stop tool router: accepts a natural language task description, returns recommended tools and next' — routes to and potentially triggers other tools on a server that includes exploit analysis, ROP chain building, browser automation, and security auditing…

The rule that runs route_tool safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For route_tool, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "route_tool": {
      "limits": [
        {
          "counter": "route_tool_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about route_tool