Get current PID controller settings for roll, pitch, and yaw
AI agents call get_pid_settings 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 existing PID (proportional-integral-derivative) controller parameters from the drone flight controller. It performs a passive read operation that returns configuration state without altering any settings, executing commands, or triggering hardware actions. The verb 'Get' and the absence of any modification language confirm this is a non-destructive data retrieval operation.
From the tool's definition Tool name 'get_pid_settings' with description 'Get current PID controller settings for roll, pitch, and yaw' indicates retrieval of configuration data with no modification or side effects.
Attacks that exploit this kind of access
Get current PID controller settings for roll, pitch, and yaw. 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_pid_settings: 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_pid_settings 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_pid_settings 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_pid_settings. 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_pid_settings 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_pid_settings 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 →