set_osd_element · Betaflight MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_osd_element does on Betaflight MCP Server

AI agents use set_osd_element 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 set_osd_element needs a policy

This tool creates or modifies OSD element configuration reversibly. While it affects drone behavior, it does not execute arbitrary commands, delete data irreversibly, or move financial resources. The modification is limited to visual display elements on the FPV feed, which can be undone by repositioning or re-toggling elements.

From the tool's definition Tool description states 'Position and toggle an individual OSD element' — this modifies OSD (On-Screen Display) configuration by changing element positions and state, which are reversible changes to the drone's display settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_osd_element Rate-limited

set_osd_element 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": {
    "set_osd_element": {
      "limits": [
        {
          "counter": "set_osd_element_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 set_osd_element

What does the set_osd_element tool do? +

Position and toggle an individual OSD element. 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 set_osd_element? +

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

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

Can I rate-limit set_osd_element? +

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

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

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