Low Risk

route_trade

Get ordered list of available markets for executing a trade. Returns spot, perp, and DEX venues based on available wallet chains.

How to control route_trade ↓

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

Low Risk

The tool retrieves and returns an ordered list of available markets/venues — it does not execute a trade itself. However, given the server context (cryptocurrency trading, payments) and that this tool's output would directly inform/enable financial trade execution, the severity is elevated to medium. The description says 'Get' and 'Returns', indicating a read/query operation.

From the tool's definition Get ordered list of available markets for executing a trade. Returns spot, perp, and DEX venues based on available wallet chains.

Documented attack patterns abuse exactly the kind of access route_trade gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Agenti, and nothing reaches the server without passing your rules. This is the rule we recommend for route_trade:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "route_trade": {}
  }
}

route_trade is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Agenti — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the route_trade tool do? +

Get ordered list of available markets for executing a trade. Returns spot, perp, and DEX venues based on available wallet chains. It is categorised as a Read tool in the Agenti MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on route_trade? +

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

What risk level is route_trade? +

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

Can I rate-limit route_trade? +

Yes. Add a rate_limit block to the route_trade 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_trade completely? +

Set action: deny in the PolicyLayer policy for route_trade. 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_trade? +

route_trade is provided by the Agenti MCP server (nirholas/agenti). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Agenti tool call.

Deterministic rules across all 73 Agenti tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

73 Agenti tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.