disconnect_flight_controller · Betaflight MCP Server MCP

WHAT IT DOES

What disconnect_flight_controller does on Betaflight MCP Server

AI agents use disconnect_flight_controller to create or update resources in Betaflight MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Betaflight MCP Server environment.

WHY IT NEEDS A POLICY

Why disconnect_flight_controller needs a policy

An AI agent can call disconnect_flight_controller faster than any human can review — one bad instruction and it creates or modifies resources in Betaflight MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disconnect_flight_controller Rate-limited

disconnect_flight_controller stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "disconnect_flight_controller": {
      "limits": [
        {
          "counter": "disconnect_flight_controller_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Betaflight MCP Server, so you can run agents against it safely.

FAQ

Questions about disconnect_flight_controller

What does the disconnect_flight_controller tool do? +

Disconnect from the flight controller. It is categorised as a Write tool in the Betaflight MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on disconnect_flight_controller? +

Register the Betaflight MCP Server MCP server in PolicyLayer and add a rule for disconnect_flight_controller: 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 Betaflight MCP Server. Nothing to install.

What risk level is disconnect_flight_controller? +

disconnect_flight_controller is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit disconnect_flight_controller? +

Yes. Add a rate_limit block to the disconnect_flight_controller 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 disconnect_flight_controller completely? +

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

disconnect_flight_controller is provided by the Betaflight MCP Server MCP server (jir13/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.