brightness_display

Read or adjust brightness on the focused display and report the measured value afterwards.

SERVEROmarchy-MCP SOURCEhlsitechio/Omarchy-MCP

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/omarchy-mcp/brightness-display.md

WHAT IT DOES

What brightness_display does on Omarchy-MCP

AI agents invoke brightness_display to trigger actions in Omarchy-MCP. 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.

RISK

Why brightness_display is rated High

Can modify display brightness settings, triggering external hardware changes on the system.

From the tool's definition Read or adjust brightness on the focused display

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs brightness_display safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Omarchy-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For brightness_display, this is the rule to start with:

brightness_display Rate-limited

brightness_display 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "brightness_display": {
      "limits": [
        {
          "counter": "brightness_display_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Omarchy-MCP, apply this rule, and every brightness_display call is checked against it from then on.

FAQ

Questions about brightness_display

What does the brightness_display tool do? +

Read or adjust brightness on the focused display and report the measured value afterwards. It is categorised as a Execute tool in the Omarchy-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on brightness_display? +

Register the Omarchy MCP server in PolicyLayer and add a rule for brightness_display: 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 Omarchy-MCP. Nothing to install.

What risk level is brightness_display? +

brightness_display is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit brightness_display? +

Yes. Add a rate_limit block to the brightness_display 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.

How do I block brightness_display completely? +

Set action: deny in the PolicyLayer policy for brightness_display. 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.

What MCP server provides brightness_display? +

brightness_display is provided by the Omarchy MCP server (hlsitechio/Omarchy-MCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Omarchy, and thousands of servers like it.

This server

All 466 Omarchy tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →