getAcrossRoutes

Discover exact Across token pairs and native ETH routes on requested networks. Empty means no listed routes; failed requests remain unknown. Deployment configuration is separate.

SERVERAgentek Eth SOURCEnanidao/agentek

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/nanidao-agentek/getacrossroutes.md

WHAT IT DOES

What getAcrossRoutes does on Agentek Eth

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

RISK

Why getAcrossRoutes is rated Low

Queries and retrieves token route information without modifying state.

From the tool's definition Discover routes; returns data; no side effects

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getAcrossRoutes safely

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

getAcrossRoutes Allowed

getAcrossRoutes 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": {
    "getAcrossRoutes": {}
  }
}

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

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

FAQ

Questions about getAcrossRoutes

What does the getAcrossRoutes tool do? +

Discover exact Across token pairs and native ETH routes on requested networks. Empty means no listed routes; failed requests remain unknown. Deployment configuration is separate. It is categorised as a Read tool in the Agentek Eth MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getAcrossRoutes? +

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

What risk level is getAcrossRoutes? +

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

Can I rate-limit getAcrossRoutes? +

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

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

getAcrossRoutes is provided by the Agentek Eth MCP server (nanidao/agentek). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Agentek Eth, and thousands of servers like it.

This server

All 212 Agentek Eth tools →

Across the catalogue

The MCP Attack Database →

Guides

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