memory_update

Update name, tags, or qualities on an existing technique. Qualities are merged (lists replace).

SERVERLivepilot SOURCElivepilot

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dreamrec-livepilot/memory-update.md

WHAT IT DOES

What memory_update does on Livepilot

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

RISK

Why memory_update is rated Medium

This is a Write operation because it modifies existing data reversibly within Ableton Live's session memory system. It changes metadata (name, tags, qualities) on technique records rather than creating new tools or destructively removing data.

From the tool's definition The tool 'memory_update' performs an update operation on existing data: 'Update name, tags, or qualities on an existing technique.' The description explicitly states it modifies stored technique records by changing their attributes and merging qualities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs memory_update safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Livepilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For memory_update, this is the rule to start with:

memory_update Rate-limited

memory_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": {
    "memory_update": {
      "limits": [
        {
          "counter": "memory_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every memory_update call is checked against it from then on.

FAQ

Questions about memory_update

What does the memory_update tool do? +

Update name, tags, or qualities on an existing technique. Qualities are merged (lists replace). It is categorised as a Write tool in the Livepilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory_update? +

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

What risk level is memory_update? +

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

Can I rate-limit memory_update? +

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

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

memory_update is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Livepilot, and thousands of servers like it.

This server

All 474 Livepilot tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →