route_request

A read tool on the Livepilot MCP server.

SERVERLivepilot SOURCElivepilot

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dreamrec-livepilot/route-request.md

WHAT IT DOES

What route_request does on Livepilot

AI agents call route_request to retrieve information from Livepilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why route_request is rated Low

Even though route_request only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs route_request safely

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

route_request Allowed

route_request is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "route_request": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every route_request call is checked against it from then on.

FAQ

Questions about route_request

What does the route_request tool do? +

route_request is a read tool on the Livepilot MCP server. It is categorised as a Read tool in the Livepilot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on route_request? +

Register the Livepilot MCP server in PolicyLayer and add a rule for route_request: 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 Livepilot. Nothing to install.

What risk level is route_request? +

route_request is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit route_request? +

Yes. Add a rate_limit block to the route_request 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.

How do I block route_request completely? +

Set action: deny in the PolicyLayer policy for route_request. 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.

What MCP server provides route_request? +

route_request is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Livepilot, and thousands of servers like it.

This server

All 474 Livepilot tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →