Updates task properties including completion status, progress percentage, notes, and blockers. Progress notes are automatically timestamped.
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.
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:
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:
{
"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.
Free to start. No card required.
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.
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.
update_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
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.