freqtrade_get_config_schema
AI agents call freqtrade_get_config_schema 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 schema metadata about Freqtrade configuration—a non-destructive, informational operation. The read-only nature of the server and the pattern of sibling tools all performing queries/retrievals confirm this is a Read operation. Low severity because schema information is typically non-sensitive and provides no direct control over trading systems.
From the tool's definition Tool name 'freqtrade_get_config_schema' indicates retrieval of configuration schema information. Server is explicitly described as 'read-only' providing 'introspection data and documentation'. All sibling tools are read operations (get_*, list_*).
Documented attack patterns abuse exactly the kind of access freqtrade_get_config_schema 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 freqtrade_get_config_schema:
{
"version": "1",
"default": "deny",
"tools": {
"freqtrade_get_config_schema": {}
}
}freqtrade_get_config_schema 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.
freqtrade_get_config_schema. 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 freqtrade_get_config_schema: 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.
freqtrade_get_config_schema 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 freqtrade_get_config_schema 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 freqtrade_get_config_schema. 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.
freqtrade_get_config_schema is provided by the Freqtrade MCP server (yalcin/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.
13 Freqtrade tools catalogued and risk-classified — across an index of 43,000+ MCP servers.