List all DEX aggregators and AMMs that Relay routes swaps through (e.g. Uniswap, Jupiter, SushiSwap). Use this to answer
AI agents call get_swap_sources to retrieve information from Relay MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about supported swap sources (DEX aggregators and AMMs) but does not execute swaps, transfer funds, or modify any state. It is purely informational, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'get_swap_sources' and description 'List all DEX aggregators and AMMs' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List all DEX aggregators and AMMs that Relay routes swaps through (e.g. Uniswap, Jupiter, SushiSwap). Use this to answer. It is categorised as a Read tool in the Relay MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Relay MCP Server MCP server in PolicyLayer and add a rule for get_swap_sources: 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 Relay MCP Server. Nothing to install.
get_swap_sources 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 get_swap_sources 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 get_swap_sources. 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.
get_swap_sources is provided by the Relay MCP Server MCP server (relayprotocol/relay-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →