add_record · Pg Mnemosyne MCP: Risk & Policy

WHAT IT DOES

What add_record does on Pg Mnemosyne

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

WHY IT NEEDS A POLICY

Why add_record needs a policy

The tool creates new records in a database without irreversibly destroying data. While the blast radius is medium (an agent could add many spurious records, polluting the database), this is reversible. The tool does not execute arbitrary code, move money, or permanently delete data, so Write is the appropriate category. Confidence is high given the clear action descriptor in the tool name and description.

From the tool's definition Tool description states 'Adds a new memory/task record' — this creates new data in the PostgreSQL database. The verb 'adds' indicates data creation/insertion, which is reversible via delete_record (a sibling tool), making this Write rather than Destructive.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_record Rate-limited

add_record 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_record": {
      "limits": [
        {
          "counter": "add_record_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 Pg Mnemosyne, so you can run agents against it safely.

FAQ

Questions about add_record

What does the add_record tool do? +

Adds a new memory/task record. It is categorised as a Write tool in the Pg Mnemosyne 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_record? +

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

What risk level is add_record? +

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

Can I rate-limit add_record? +

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

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

add_record is provided by the Pg Mnemosyne MCP server (janadasroor/pg-mnemosyne-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.