self_window_info

Resolve and report the terminal window this agent is running in, by walking PID ancestry — like Windows

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/self-window-info.md

WHAT IT DOES

What self_window_info does on Omarchy-MCP

AI agents call self_window_info 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 self_window_info is rated Low

Tool queries process ancestry to identify running window; no modification or system commands.

From the tool's definition Resolve and report terminal window this agent is running in

Attacks that exploit this kind of access

RECOMMENDED RULE

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

self_window_info Allowed

self_window_info 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": {
    "self_window_info": {}
  }
}

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 self_window_info call is checked against it from then on.

FAQ

Questions about self_window_info

What does the self_window_info tool do? +

Resolve and report the terminal window this agent is running in, by walking PID ancestry — like Windows. 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 self_window_info? +

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

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

Can I rate-limit self_window_info? +

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

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

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