Get onboard dataflash memory status (used/total space for blackbox)
AI agents call get_dataflash_summary 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 merely queries and reports the current state of onboard memory—specifically how much blackbox storage is used versus total available. It performs no modifications, deletions, or commands that would alter flight controller state or data. It is a pure read operation returning informational metrics.
From the tool's definition Tool name 'get_dataflash_summary' and description 'Get onboard dataflash memory status (used/total space for blackbox)' indicate a query operation that retrieves status information without modifying or executing operations.
Attacks that exploit this kind of access
Get onboard dataflash memory status (used/total space for blackbox). 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_dataflash_summary: 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_dataflash_summary 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_dataflash_summary 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_dataflash_summary. 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_dataflash_summary 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 →