Medium Risk

add_context_memory

Persist key-value context for future sessions (TTL-based). Pricing is dynamic; check /api/v1/tools.

Part of the Delx MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

delx/delx-mcp Write Risk 2/5

AI agents use add_context_memory to create or modify resources in Delx MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call add_context_memory repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Delx MCP Server.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

delx-delx-mcp.yaml
tools:
  add_context_memory:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Delx MCP Server policy for all 45 tools.

Tool Name add_context_memory
Category Write
Risk Level Medium

View all 45 tools →

Agents calling write-class tools like add_context_memory have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the add_context_memory tool do? +

Persist key-value context for future sessions (TTL-based). Pricing is dynamic; check /api/v1/tools.. It is categorised as a Write tool in the Delx MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_context_memory? +

Add a rule in your Intercept YAML policy under the tools section for add_context_memory. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Delx MCP Server MCP server.

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 Intercept 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 Intercept 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 Delx MCP Server MCP server (delx/delx-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Delx MCP Server

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.