pulse_update_task · Pulse MCP: Risk & Policy

WHAT IT DOES

What pulse_update_task does on Pulse

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

WHY IT NEEDS A POLICY

Why pulse_update_task needs a policy

This tool creates or modifies data reversibly by allowing updates to task attributes (title, description, status, tags). Changes can be undone by subsequent updates. It does not execute code, delete data irreversibly, or move money. Severity is medium because an agent could spam task updates or corrupt task metadata, but the impact is limited to task records and reversible.

From the tool's definition Tool name 'pulse_update_task' and description 'Update a task or subtask (title/status; description is task-only)' clearly indicate modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pulse_update_task Rate-limited

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

FAQ

Questions about pulse_update_task

What does the pulse_update_task tool do? +

Update a task or subtask (title/status; description is task-only). At least one update field (title, description, status, or tag) must be provided. It is categorised as a Write tool in the Pulse MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pulse_update_task? +

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

What risk level is pulse_update_task? +

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

Can I rate-limit pulse_update_task? +

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

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

pulse_update_task is provided by the Pulse MCP server (nemesiscodex/pulse-tm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.