Get OSD (on-screen display) configuration
AI agents call get_osd_config to retrieve information from Betaflight MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves OSD configuration settings from the flight controller. It queries existing configuration state with no side effects, modifications, or external operations triggered. This is a pure read operation with minimal blast radius if misused by an AI agent — at worst, it would expose configuration details already stored on the device.
From the tool's definition Tool name is 'get_osd_config' and description states 'Get OSD (on-screen display) configuration' — the verb 'Get' indicates retrieval of configuration data without modification.
Attacks that exploit this kind of access
Get OSD (on-screen display) configuration. It is categorised as a Read tool in the Betaflight MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Betaflight MCP Server MCP server in PolicyLayer and add a rule for get_osd_config: 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.
get_osd_config 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 get_osd_config 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 get_osd_config. 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.
get_osd_config 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →