Set screen brightness (0-255). Requires Shizuku/ADB.
AI agents use set_screen_brightness to create or update resources in Android MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Android MCP Server environment.
This tool modifies a device display setting (screen brightness) which is a reversible write operation. It changes a system setting but has no destructive, financial, or code-execution implications. Blast radius is low — misuse would only alter display brightness, which is trivially reversible.
From the tool's definition Set screen brightness (0-255)
Attacks that exploit this kind of access
Set screen brightness (0-255). Requires Shizuku/ADB. It is categorised as a Write tool in the Android MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Android MCP Server MCP server in PolicyLayer and add a rule for set_screen_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 Android MCP Server. Nothing to install.
set_screen_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_screen_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_screen_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_screen_brightness is provided by the Android MCP Server MCP server (wujie272/android-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 →