workspace_plan_update · TermPipe MCP: Risk & Policy

WHAT IT DOES

What workspace_plan_update does on TermPipe MCP

AI agents use workspace_plan_update 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 workspace_plan_update needs a policy

The tool appears to modify workspace state ('update' indicates Write rather than Read). Without explicit description, confidence is reduced but not eliminated by the naming convention and server context. It does not appear to delete data (Destructive), execute arbitrary commands (Execute), or involve financial transactions.

From the tool's definition Tool name 'workspace_plan_update' combined with server description indicating file management and persistent state control suggests data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

workspace_plan_update Rate-limited

workspace_plan_update 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": {
    "workspace_plan_update": {
      "limits": [
        {
          "counter": "workspace_plan_update_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 workspace_plan_update

What does the workspace_plan_update tool do? +

workspace_plan_update. 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 workspace_plan_update? +

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

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

Can I rate-limit workspace_plan_update? +

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

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

workspace_plan_update 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.