cond_save_layout · TermPipe MCP: Risk & Policy

WHAT IT DOES

What cond_save_layout does on TermPipe MCP

AI agents use cond_save_layout to create or update resources in TermPipe MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TermPipe MCP environment.

WHY IT NEEDS A POLICY

Why cond_save_layout needs a policy

This tool creates or modifies persistent state (window layout configuration) without destructive effects, data deletion, or external side effects beyond the host system's window manager state. It is reversible—new layouts can be saved over old ones, and the operation does not irreversibly delete or corrupt data.

From the tool's definition The tool 'cond_save_layout' saves a current window layout to a numbered slot (1-9). This creates or modifies configuration/state data in a reversible manner—a saved layout can be overwritten or deleted.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cond_save_layout Rate-limited

cond_save_layout stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cond_save_layout": {
      "limits": [
        {
          "counter": "cond_save_layout_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TermPipe MCP, so you can run agents against it safely.

FAQ

Questions about cond_save_layout

What does the cond_save_layout tool do? +

Save current window layout to a numbered slot (1-9). It is categorised as a Write tool in the TermPipe MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cond_save_layout? +

Register the TermPipe MCP server in PolicyLayer and add a rule for cond_save_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 TermPipe MCP. Nothing to install.

What risk level is cond_save_layout? +

cond_save_layout is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cond_save_layout? +

Yes. Add a rate_limit block to the cond_save_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.

How do I block cond_save_layout completely? +

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

What MCP server provides cond_save_layout? +

cond_save_layout is provided by the TermPipe MCP server (wbind-core/termpipe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.