memory_import · Jt MCP: Risk & Policy

WHAT IT DOES

What memory_import does on Jt

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

WHY IT NEEDS A POLICY

Why memory_import needs a policy

This tool creates or modifies data in a reversible manner. The merge mode adds to existing knowledge graph data, and replace mode overwrites it—both are Write operations. While replace mode approaches destructiveness, the operation targets a structured data store (knowledge graph) rather than irreversibly deleting files or records, and the data can be recovered or reimported.

From the tool's definition Tool description explicitly states 'Import a knowledge graph from JSON' with options to 'add to existing data' (merge mode) or 'start fresh' (replace mode). The 'replace mode' capability modifies existing data structures.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_import Rate-limited

memory_import 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": {
    "memory_import": {
      "limits": [
        {
          "counter": "memory_import_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 Jt, so you can run agents against it safely.

FAQ

Questions about memory_import

What does the memory_import tool do? +

Import a knowledge graph from JSON. Use merge mode to add to existing data, or replace mode to start fresh. It is categorised as a Write tool in the Jt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory_import? +

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

What risk level is memory_import? +

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

Can I rate-limit memory_import? +

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

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

memory_import is provided by the Jt MCP server (@houkasaurusrex/jt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.