Low Risk

fetch_bot_status

Retrieve the current status of open trades. Parameters: ctx (Context): MCP context object for logging and client access. Returns: str: Stringified JSON response with open trade status, or None if failed.

How to control fetch_bot_status ↓

What fetch_bot_status does on Freqtrade

AI agents call fetch_bot_status 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.

Low Risk

Why fetch_bot_status needs a policy

This tool retrieves and returns information about open trades in a read-only manner. There are no indications of data modification, deletion, execution of commands, or financial transactions. The function simply fetches and returns the current status, which is a benign read operation with minimal security risk.

From the tool's definition Tool name 'fetch_bot_status' and description 'Retrieve the current status of open trades' indicate a read operation that queries data without modification or side effects.

Documented attack patterns abuse exactly the kind of access fetch_bot_status gives an agent:

How to control fetch_bot_status

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_bot_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "fetch_bot_status": {}
  }
}

fetch_bot_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Freqtrade — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about fetch_bot_status

What does the fetch_bot_status tool do? +

Retrieve the current status of open trades. Parameters: ctx (Context): MCP context object for logging and client access. Returns: str: Stringified JSON response with open trade status, or None if failed. It is categorised as a Read tool in the Freqtrade MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch_bot_status? +

Register the Freqtrade MCP server in PolicyLayer and add a rule for fetch_bot_status: 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.

What risk level is fetch_bot_status? +

fetch_bot_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fetch_bot_status? +

Yes. Add a rate_limit block to the fetch_bot_status 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.

How do I block fetch_bot_status completely? +

Set action: deny in the PolicyLayer policy for fetch_bot_status. 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.

What MCP server provides fetch_bot_status? +

fetch_bot_status 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.

Enforce policy on every Freqtrade tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.