Get current PID profile (1-3) and rate profile (1-6)
AI agents call get_current_profile 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 queries and retrieves the current active PID and rate profile identifiers from the flight controller. It performs a read-only operation with no side effects, no code execution, and no data modification. The retrieved information is purely informational about the existing configuration state.
From the tool's definition Tool name 'get_current_profile' and description 'Get current PID profile (1-3) and rate profile (1-6)' indicate retrieval of configuration state with no modification or execution of commands.
Attacks that exploit this kind of access
Get current PID profile (1-3) and rate profile (1-6). 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_current_profile: 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_current_profile 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_current_profile 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_current_profile. 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_current_profile 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.
get_current_profile is one line of Betaflight MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →