Save the current window arrangement as a new Moom layout
AI agents use save_current_layout to create or update resources in Moom MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Moom MCP Server environment.
This tool creates new persistent layout data without deleting or overwriting existing layouts. While it modifies the application's stored layouts, the action is reversible (the saved layout can be deleted or overwritten later). It does not execute arbitrary code, move money, or permanently destroy data.
From the tool's definition Tool description states 'Save the current window arrangement as a new Moom layout' — this creates and stores a new layout configuration, a reversible write operation.
Attacks that exploit this kind of access
Save the current window arrangement as a new Moom layout. It is categorised as a Write tool in the Moom MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Moom MCP Server MCP server in PolicyLayer and add a rule for save_current_layout: 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 Moom MCP Server. Nothing to install.
save_current_layout 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 save_current_layout 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 save_current_layout. 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.
save_current_layout is provided by the Moom MCP Server MCP server (itrimble/moom-mcp). 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 →