AI agents call delete_blacklist to permanently remove resources in Freqtrade — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name strongly suggests deletion of blacklist entries in a cryptocurrency trading bot context. Removing items from a trading blacklist could allow the bot to trade previously banned assets, potentially leading to significant financial or operational harm. Deletion operations are typically irreversible, placing this in the Destructive category. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'delete_blacklist' implies irreversible removal of entries from the trading blacklist; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access delete_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 delete_blacklist:
{
"version": "1",
"default": "deny",
"hide": [
"delete_blacklist"
]
} delete_blacklist disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete_blacklist. It is categorised as a Destructive tool in the Freqtrade MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Freqtrade MCP server in PolicyLayer and add a rule for delete_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.
delete_blacklist is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.