workspace_task_update · TermPipe MCP: Risk & Policy

WHAT IT DOES

What workspace_task_update does on TermPipe MCP

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

The tool name suggests updating a task within a workspace, which implies a write operation. However, the description is empty, so the exact behavior is unknown. Given the server's capabilities (terminal access, file management), this could be more severe, but 'update' typically implies a reversible write operation. Confidence is low due to the lack of description.

From the tool's definition Tool name 'workspace_task_update' and empty description. Server provides terminal access, file management, and REPL sessions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

workspace_task_update Rate-limited

workspace_task_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_task_update": {
      "limits": [
        {
          "counter": "workspace_task_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_task_update

What does the workspace_task_update tool do? +

workspace_task_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_task_update? +

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

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

Can I rate-limit workspace_task_update? +

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

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

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