Low Risk

fetch_whitelist

Get the current whitelist of trading pairs. Parameters: ctx (Context): MCP context object for logging and client access. Returns: str: Stringified JSON response with whitelist data, or None if failed.

How to control fetch_whitelist ↓

What fetch_whitelist does on Freqtrade

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

Low Risk

Why fetch_whitelist needs a policy

This tool retrieves configuration data (the whitelist of trading pairs) without modifying, executing, or deleting anything. It is a read-only operation with no side effects. The low severity reflects minimal risk even if misused, as it only exposes the list of pairs the bot is configured to trade.

From the tool's definition Tool name is 'fetch_whitelist' and description states 'Get the current whitelist of trading pairs.' The verb 'fetch' and 'get' indicate data retrieval with no modifications. Returns stringified JSON with whitelist data.

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

How to control fetch_whitelist

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

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

fetch_whitelist 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 Freqtrade — 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.

Related tools and policies

Go deeper

Questions about fetch_whitelist

What does the fetch_whitelist tool do? +

Get the current whitelist of trading pairs. Parameters: ctx (Context): MCP context object for logging and client access. Returns: str: Stringified JSON response with whitelist data, or None if failed. It is categorised as a Read tool in the Freqtrade MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch_whitelist? +

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

What risk level is fetch_whitelist? +

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

Can I rate-limit fetch_whitelist? +

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

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

fetch_whitelist is provided by the Freqtrade MCP server (kukapay/freqtrade-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Freqtrade tool call.

Start from Freqtrade, 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.

17 Freqtrade tools catalogued and risk-classified — across an index of 43,000+ 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.