task.update · Freedcamp MCP Server MCP: Risk & Policy

WHAT IT DOES

What task.update does on Freedcamp MCP Server

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

WHY IT NEEDS A POLICY

Why task.update needs a policy

This tool modifies existing task data reversibly. While it can change task state (including potentially marking tasks as complete or changing assignments), it does not delete data permanently, nor does it execute arbitrary code or move money. The high severity reflects that mass task updates could disrupt project workflows and cause significant inconvenience, but the changes are reversible through subsequent updates.

From the tool's definition Tool name 'task.update' combined with description 'Update an existing task. Only provided fields are changed' indicates modification of existing data. The sibling tool context includes 'task' operations in a project management system with authentication.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

task.update Rate-limited

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": {
    "task.update": {
      "limits": [
        {
          "counter": "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 Freedcamp MCP Server, so you can run agents against it safely.

FAQ

Questions about task.update

What does the task.update tool do? +

Update an existing task. Only provided fields are changed. Accepts string status labels or numeric codes. It is categorised as a Write tool in the Freedcamp MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on task.update? +

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

What risk level is task.update? +

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

Can I rate-limit task.update? +

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

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

task.update is provided by the Freedcamp MCP Server MCP server (mahrukh-n8n/freedcampmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.