Medium Risk

update_task

Updates task properties including completion status, progress percentage, notes, and blockers. Progress notes are automatically timestamped.

How to control update_task ↓

What update_task does on Memory Pickle MCP

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

Medium Risk

Why update_task needs a policy

This tool modifies task metadata (completion status, progress, notes, blockers) but does not delete data or execute arbitrary code. Changes are reversible through subsequent updates.

From the tool's definition Tool description states it 'Updates task properties including completion status, progress percentage, notes, and blockers.' The verb 'Updates' indicates modification of existing data.

Documented attack patterns abuse exactly the kind of access update_task gives an agent:

How to control update_task

PolicyLayer is an MCP gateway — it sits between your AI agents and Memory Pickle MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for update_task:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_task": {
      "limits": [
        {
          "counter": "update_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

  1. Create a free account and register Memory Pickle MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about update_task

What does the update_task tool do? +

Updates task properties including completion status, progress percentage, notes, and blockers. Progress notes are automatically timestamped. It is categorised as a Write tool in the Memory Pickle 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 update_task? +

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

What risk level is update_task? +

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

Can I rate-limit update_task? +

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

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

update_task is provided by the Memory Pickle MCP server (justar96/memory-pickle). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Memory Pickle MCP tool call.

Start from Memory Pickle MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

13 Memory Pickle MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.