tb_update · Forgespec MCP: Risk & Policy

WHAT IT DOES

What tb_update does on Forgespec

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

WHY IT NEEDS A POLICY

Why tb_update needs a policy

The tool creates or modifies task data reversibly within the task board system. Updates can be undone or corrected, and there are no indications of irreversible deletion, code execution, or financial operations.

From the tool's definition Tool name 'tb_update' and description 'Update a task' indicate modification of task board data. Context shows this is part of task board management ('tb_' prefix with other tools like tb_add_task, tb_claim, tb_create_board), which manages workflow state in a…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tb_update Rate-limited

tb_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": {
    "tb_update": {
      "limits": [
        {
          "counter": "tb_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 Forgespec, so you can run agents against it safely.

FAQ

Questions about tb_update

What does the tb_update tool do? +

Update a task. It is categorised as a Write tool in the Forgespec MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on tb_update? +

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

What risk level is tb_update? +

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

Can I rate-limit tb_update? +

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

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

tb_update is provided by the Forgespec MCP server (lleontor705/forgespec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.