Delete a specific trade lock by ID. Parameters: lock_id (int): ID of the trade lock to delete. ctx (Context): MCP context object for logging and client access. Returns: str: Stringified JSON response with updated locks, or error if failed.
AI agents call delete_lock 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.
This tool permanently removes a trade lock from the Freqtrade system. Trade locks are constraints on trading pairs (typically used to prevent trading on certain pairs after losses or other conditions). Deleting a lock is irreversible and could allow trading to resume on a pair that was intentionally locked, potentially exposing the bot to unwanted trades.
From the tool's definition Tool name 'delete_lock' and description 'Delete a specific trade lock by ID' indicate irreversible deletion of data. The lock_id parameter specifies which lock to remove, and the operation cannot be undone.
Documented attack patterns abuse exactly the kind of access delete_lock 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_lock:
{
"version": "1",
"default": "deny",
"hide": [
"delete_lock"
]
}delete_lock 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 a specific trade lock by ID. Parameters: lock_id (int): ID of the trade lock to delete. ctx (Context): MCP context object for logging and client access. Returns: str: Stringified JSON response with updated locks, or error if failed. 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_lock: 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_lock 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_lock 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_lock. 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_lock 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.