lithtrix_memory_set · Lithtrix MCP: Risk & Policy

WHAT IT DOES

What lithtrix_memory_set does on Lithtrix

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

WHY IT NEEDS A POLICY

Why lithtrix_memory_set needs a policy

The tool creates or updates memory entries in persistent storage. While this modifies state, it is reversible via subsequent writes or deletes (evidenced by the sibling lithtrix_blob_delete tool). The severity is medium because uncontrolled memory writes by a compromised agent could corrupt shared state across vendors and sessions, but the effect is not permanent destruction and can be corrected.

From the tool's definition Tool description states 'Store or update a JSON value for a memory key' and uses HTTP PUT method, which creates or modifies data reversibly. This is a write operation without destructive intent.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lithtrix_memory_set Rate-limited

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Lithtrix, so you can run agents against it safely.

FAQ

Questions about lithtrix_memory_set

What does the lithtrix_memory_set tool do? +

Store or update a JSON value for a memory key (PUT /v1/memory/{key}). It is categorised as a Write tool in the Lithtrix MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on lithtrix_memory_set? +

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

What risk level is lithtrix_memory_set? +

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

Can I rate-limit lithtrix_memory_set? +

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

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

lithtrix_memory_set is provided by the Lithtrix MCP server (lithtrix/lithtrix-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.