upload_artifact · Mnemosyne MCP: Risk & Policy

WHAT IT DOES

What upload_artifact does on Mnemosyne MCP

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

WHY IT NEEDS A POLICY

Why upload_artifact needs a policy

The tool uploads an artifact (likely RDF/knowledge graph data) into Mnemosyne. This is a reversible data creation/modification operation (Write category). Severity is medium because unintended uploads could pollute the knowledge graph, but the effects are theoretically reversible (suggested by sibling 'archive_memories' and 'delete' tools).

From the tool's definition Tool name 'upload_artifact' combined with server context describing 'RDF file uploads' and 'graph operations' indicates the tool creates or modifies data in the knowledge graph.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_artifact Rate-limited

upload_artifact 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": {
    "upload_artifact": {
      "limits": [
        {
          "counter": "upload_artifact_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 Mnemosyne MCP, so you can run agents against it safely.

FAQ

Questions about upload_artifact

What does the upload_artifact tool do? +

upload_artifact. It is categorised as a Write tool in the Mnemosyne MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on upload_artifact? +

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

What risk level is upload_artifact? +

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

Can I rate-limit upload_artifact? +

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

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

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