Get the current trade locks. Parameters: ctx (Context): MCP context object for logging and client access. Returns: str: Stringified JSON response with trade locks data, or None if failed.
AI agents call fetch_locks 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.
This tool retrieves and queries existing trade lock data from the Freqtrade bot without creating, modifying, deleting, or executing any operations. It is purely informational and read-only, making it a Read category tool with low severity.
From the tool's definition Tool name 'fetch_locks' and description 'Get the current trade locks' indicate a retrieval operation with no modification of state. Returns 'Stringified JSON response with trade locks data' with no side effects.
Documented attack patterns abuse exactly the kind of access fetch_locks 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 fetch_locks:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_locks": {}
}
}fetch_locks 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.
Get the current trade locks. Parameters: ctx (Context): MCP context object for logging and client access. Returns: str: Stringified JSON response with trade locks 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.
Register the Freqtrade MCP server in PolicyLayer and add a rule for fetch_locks: 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.
fetch_locks 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 fetch_locks 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 fetch_locks. 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.
fetch_locks 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.