This record as markdown: /tools/heznpc-airmcp/set-brightness.md
What set_brightness does on AirMCP
AI agents invoke set_brightness to trigger actions in AirMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why set_brightness is rated High
Changing display brightness is an external system operation that modifies hardware state. It is not a simple data read or write to a data store, but rather an execution of a system control action. The description is truncated ('Requires the...') but the core action is clear. Misuse could impair usability (e.g., setting brightness to 0), hence medium severity.
From the tool's definition 'Set the display brightness level' — triggers a system-level hardware/display setting change
Attacks that exploit this kind of access
The rule that runs set_brightness safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_brightness, this is the rule to start with:
set_brightness stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every set_brightness call is checked against it from then on.
Questions about set_brightness
Set the display brightness level. Requires the. It is categorised as a Execute tool in the AirMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Air MCP server in PolicyLayer and add a rule for set_brightness: 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 AirMCP. Nothing to install.
set_brightness is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the set_brightness 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 set_brightness. 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.
set_brightness is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue