add_context_memory

Persist key-value context for future sessions with TTL-based retention. Free.

SERVERWitness Protocol SOURCEdelx/witness-protocol

Medium RISK CLASS

Category Write

Parameters 40 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/delx-witness-protocol/add-context-memory.md

WHAT IT DOES

What add_context_memory does on Witness Protocol

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

Parameter	Type	Required	Description
`key`	string	—	Context key
`value`	string	—	Context value
`ttl_hours`	integer	—	Optional retention window in hours
`session_id`	string	—	Your active session ID

Parameters from the server's own tool schema.

RISK

Why add_context_memory is rated Medium

This tool writes/creates persistent data (key-value pairs) into a storage system for future retrieval. While the data is reversible (TTL-based retention means it eventually expires automatically, and likely can be deleted), it modifies application state.

From the tool's definition Tool description states 'Persist key-value context for future sessions with TTL-based retention' — the verb 'Persist' and operation of storing data indicates a write operation that creates or modifies data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs add_context_memory safely

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

add_context_memory Rate-limited

add_context_memory 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": {
    "add_context_memory": {
      "limits": [
        {
          "counter": "add_context_memory_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 Witness Protocol, apply this rule, and every add_context_memory call is checked against it from then on.

FAQ

Questions about add_context_memory

What does the add_context_memory tool do? +

Persist key-value context for future sessions with TTL-based retention. Free. It is categorised as a Write tool in the Witness Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does add_context_memory accept? +

add_context_memory accepts 4 parameters: key, value, ttl_hours, session_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on add_context_memory? +

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

What risk level is add_context_memory? +

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

Can I rate-limit add_context_memory? +

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

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

add_context_memory is provided by the Witness Protocol MCP server (delx/witness-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Witness Protocol, and thousands of servers like it.

This server

All 54 Witness Protocol tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb →team_manager_write_memory on Team Manager MCP → The MCP Attack Database →

Guides

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