Retrieves a list of all options for decentralized exchanges (DEXs) currently indexed and supported by the API. This serves as the discovery endpoint for clients to programmatically identify valid DEX identifiers used in other endpoints like trades or OHLC queries. The all option represents all DE...
AI agents call mkt-dexs to retrieve information from Maestro MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple query/lookup operation to discover valid DEX identifiers supported by the API. It has no side effects, does not execute code or transactions, and does not modify any state. It is purely informational retrieval, making it a Read category tool with low severity since misuse would only expose publicly available API metadata.
From the tool's definition Tool description states it 'Retrieves a list of all options for decentralized exchanges' and serves as a 'discovery endpoint'. The verb 'retrieves' and the read-only nature of querying available DEX options indicates no data modification or execution.
Documented attack patterns abuse exactly the kind of access mkt-dexs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Maestro MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for mkt-dexs:
{
"version": "1",
"default": "deny",
"tools": {
"mkt-dexs": {}
}
} mkt-dexs 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.
Retrieves a list of all options for decentralized exchanges (DEXs) currently indexed and supported by the API. This serves as the discovery endpoint for clients to programmatically identify valid DEX identifiers used in other endpoints like trades or OHLC queries. The all option represents all DEXs combined. It is categorised as a Read tool in the Maestro MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Maestro MCP Server MCP server in PolicyLayer and add a rule for mkt-dexs: 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 Maestro MCP Server. Nothing to install.
mkt-dexs 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 mkt-dexs 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 mkt-dexs. 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.
mkt-dexs is provided by the Maestro MCP Server MCP server (maestro-org/maestro-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Maestro MCP Server, 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.
117 Maestro MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.