AI agents use add_blacklist to create or update resources in Freqtrade — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freqtrade environment.
This tool creates or modifies blacklist entries in a cryptocurrency trading bot. Blacklists typically prevent trading on certain pairs, so adding entries reversibly changes bot trading behavior and constraints. This is Write-category (modifies data), not Destructive (since blacklist additions are reversible via delete_blacklist).
From the tool's definition Tool name 'add_blacklist' indicates modification of a blacklist data structure; context from sibling tools (delete_blacklist, fetch_blacklist) confirms blacklist is a managed dataset in a trading bot.
Documented attack patterns abuse exactly the kind of access add_blacklist gives an agent:
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 add_blacklist:
{
"version": "1",
"default": "deny",
"tools": {
"add_blacklist": {
"limits": [
{
"counter": "add_blacklist_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_blacklist stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
add_blacklist. It is categorised as a Write tool in the Freqtrade MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Freqtrade MCP server in PolicyLayer and add a rule for add_blacklist: 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.
add_blacklist is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_blacklist 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 add_blacklist. 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.
add_blacklist 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.
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.