import_graph
Import knowledge graph from various formats
This record as markdown: /tools/danielsimonjr-memory-mcp/import-graph.md
What import_graph does on Enhanced Knowledge Graph Memory Server
AI agents use import_graph to create or update resources in Enhanced Knowledge Graph Memory Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Enhanced Knowledge Graph Memory Server environment.
Why import_graph is rated Medium
Importing a knowledge graph modifies the persistent storage by adding new entities and relationships. While the operation itself is reversible (typical Write behavior), the medium severity reflects that importing untrusted or malformed data could corrupt the knowledge graph structure, cause memory bloat, or introduce erroneous relationships that affect downstream reasoning.
From the tool's definition Tool name 'import_graph' and description 'Import knowledge graph from various formats' indicate the tool creates or modifies data by ingesting external data into the knowledge graph storage system.
Attacks that exploit this kind of access
The rule that runs import_graph safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For import_graph, this is the rule to start with:
import_graph 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Enhanced Knowledge Graph Memory Server, apply this rule, and every import_graph call is checked against it from then on.
Questions about import_graph
Import knowledge graph from various formats. It is categorised as a Write tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for import_graph: 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 Enhanced Knowledge Graph Memory Server. Nothing to install.
import_graph is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the import_graph 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.
Set action: deny in the PolicyLayer policy for import_graph. 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.
import_graph is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
Across the catalogue