update_project

THE RISK

Medium Risk

Why update_project needs a policy

This tool modifies project metadata (name, description, status) but does not delete data or trigger external operations. Updates are reversible—properties can be changed again. The blast radius is minimal as this only affects project metadata within a session memory system used for AI agent context tracking, with no financial or destructive impact.

From the tool's definition Tool name 'update_project' and description 'Updates existing project properties including name, description, or status' clearly indicate modification of existing data in a reversible manner.

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

POLICY

How to control update_project

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_project:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_project": {
      "limits": [
        {
          "counter": "update_project_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

update_project 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.

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

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Memory Pickle MCP tools

Write create_project Creates a new project with specified name, description, and status. Sets the new project a Write create_task Creates a new task in the current or specified project. Supports hierarchical task organiz Write remember_this Stores information, decisions, or context with importance classification and optional link Write set_current_project Changes the active project context. Subsequent task creation operations will default to th Write update_task Updates task properties including completion status, progress percentage, notes, and block Read get_task Returns detailed information for a single task including subtasks, notes, blockers, and re Read list_projects Returns list of projects with completion statistics and optional status filtering. Include Read list_tasks Returns filtered list of tasks with pagination support. Supports filtering by status, prio

All 13 Memory Pickle MCP tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about update_project

What does the update_project tool do? +

Updates existing project properties including name, description, or status. 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_project? +

Register the Memory Pickle MCP server in PolicyLayer and add a rule for update_project: 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_project? +

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

Can I rate-limit update_project? +

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

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

update_project 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.

CHECK YOUR STACK →