bar_state

Read visibility, position, transparency, active bar, and widget layout without changing anything.

SERVEROmarchy-MCP SOURCEhlsitechio/Omarchy-MCP

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/omarchy-mcp/bar-state.md

WHAT IT DOES

What bar_state does on Omarchy-MCP

AI agents call bar_state to retrieve information from Omarchy-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why bar_state is rated Low

Retrieves UI state information with no side effects or data modification capability.

From the tool's definition Read visibility, position, transparency, active bar, and widget layout without changing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bar_state 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 bar_state, this is the rule to start with:

bar_state Allowed

bar_state is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bar_state": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about bar_state

What does the bar_state tool do? +

Read visibility, position, transparency, active bar, and widget layout without changing anything. It is categorised as a Read tool in the Omarchy-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bar_state? +

Register the Omarchy MCP server in PolicyLayer and add a rule for bar_state: 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 bar_state? +

bar_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bar_state? +

Yes. Add a rate_limit block to the bar_state 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 bar_state completely? +

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

bar_state 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 →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →