This record as markdown: /tools/io-github-heznpc-iconnect/set-brightness.md
What set_brightness does on Iconnect
AI agents use set_brightness to create or update resources in Iconnect, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iconnect environment.
Why set_brightness is rated Medium
This tool changes the display brightness, which is a reversible system configuration change. It modifies hardware/OS state but has minimal blast radius and is easily undone by setting brightness again. Fits Write category as it modifies a setting without executing code or causing destructive/financial effects.
From the tool's definition 'Set the display brightness level' — modifies a system display setting
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 Iconnect, 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 capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, 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 Write tool in the Iconnect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Iconnect 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 Iconnect. Nothing to install.
set_brightness is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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 Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue