List available Across bridge routes (supported chain/token combinations)
AI agents call routes to retrieve information from Waiaas without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that retrieves informational data about available bridge routes. It has no side effects, does not execute transactions, does not modify data, and does not move funds. The low severity reflects minimal risk even if an AI agent calls it unnecessarily—the only potential harm is wasted query resources or information disclosure, which is negligible in this context.
From the tool's definition Tool name 'routes' and description 'List available Across bridge routes' indicates a query operation that retrieves and displays supported chain/token combinations without modifying state.
Documented attack patterns abuse exactly the kind of access routes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Waiaas, and nothing reaches the server without passing your rules. This is the rule we recommend for routes:
{
"version": "1",
"default": "deny",
"tools": {
"routes": {}
}
}routes 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.
List available Across bridge routes (supported chain/token combinations). It is categorised as a Read tool in the Waiaas MCP Server, which means it retrieves data without modifying state.
Register the Waiaas MCP server in PolicyLayer and add a rule for routes: 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 Waiaas. Nothing to install.
routes 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 routes 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 routes. 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.
routes is provided by the Waiaas MCP server (minhoyoo-iotrust/waiaas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Waiaas, 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.
126 Waiaas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.