connect_flight_controller · Betaflight MCP Server MCP

WHAT IT DOES

What connect_flight_controller does on Betaflight MCP Server

AI agents invoke connect_flight_controller to trigger actions in Betaflight MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why connect_flight_controller needs a policy

This tool initiates a serial port connection to a physical drone flight controller. Establishing this connection is an external operation that triggers real-world hardware interaction. Once connected, it opens the pathway for subsequent configuration or control commands to a flight controller, making misuse potentially dangerous (e.g., connecting to the wrong device or enabling unintended control).

From the tool's definition Connect to a Betaflight flight controller via serial port

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_flight_controller Rate-limited

connect_flight_controller stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "connect_flight_controller": {
      "limits": [
        {
          "counter": "connect_flight_controller_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 connect_flight_controller

What does the connect_flight_controller tool do? +

Connect to a Betaflight flight controller via serial port. It is categorised as a Execute tool in the Betaflight MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on connect_flight_controller? +

Register the Betaflight MCP Server MCP server in PolicyLayer and add a rule for connect_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 connect_flight_controller? +

connect_flight_controller is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit connect_flight_controller? +

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

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

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