AI agents call hide_window as a supporting operation in Proxima workflows.
The tool name suggests a UI/window management action (hiding a window), which doesn't clearly map to Read, Write, Execute, Destructive, or Financial categories. Without a description, it's unclear what this does exactly. In the context of an AI gateway server, it likely hides a UI window — a benign interface action. Confidence is low due to empty description.
From the tool's definition Tool name is 'hide_window'; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access hide_window gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Proxima, and nothing reaches the server without passing your rules. This is the rule we recommend for hide_window:
{
"version": "1",
"default": "deny",
"tools": {
"hide_window": {
"limits": [
{
"counter": "hide_window_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}hide_window gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
hide_window. It is categorised as a Other tool in the Proxima MCP Server, which means it performs auxiliary operations.
Register the Proxima MCP server in PolicyLayer and add a rule for hide_window: 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 Proxima. Nothing to install.
hide_window is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hide_window 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 hide_window. 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.
hide_window is provided by the Proxima MCP server (zen4-bit/proxima). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 50 Proxima tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
50 Proxima tools catalogued and risk-classified — across an index of 42,500+ MCP servers.