AI agents use window_fullscreen to create or update resources in It2mcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your It2mcp environment.
This tool modifies the display state of a window (toggling fullscreen on/off), which is a reversible UI change. It does not execute commands, delete data, or involve financial operations. Severity is low as it only affects window presentation.
From the tool's definition Set fullscreen state for an iTerm2 window
Attacks that exploit this kind of access
Set fullscreen state for an iTerm2 window. It is categorised as a Write tool in the It2mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the It2 MCP server in PolicyLayer and add a rule for window_fullscreen: 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 It2mcp. Nothing to install.
window_fullscreen 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 window_fullscreen 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 window_fullscreen. 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.
window_fullscreen is provided by the It2 MCP server (urjitbhatia/it2mcp). 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 →