Imports Engrams data from a directory of markdown files previously created by export_engrams_to_markdown. Reads from input_path (default: ./engrams_export/). WARNING: may overwrite existing data if IDs conflict. Use for restoring backups or migrating between workspaces. Precondition: files must f...
AI agents use import_markdown_to_engrams to create or update resources in Engrams — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Engrams environment.
The tool creates or modifies data by importing engrams from markdown files, with explicit warning about potential overwrites. While it can reverse changes (data can be re-exported), the overwrite capability and potential for data loss if misused makes it Write rather than Read or Execute.
From the tool's definition Imports data and may overwrite existing data if IDs conflict. Description explicitly states: 'WARNING: may overwrite existing data if IDs conflict.' This is a data modification operation that can affect existing records.
Documented attack patterns abuse exactly the kind of access import_markdown_to_engrams gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Engrams, and nothing reaches the server without passing your rules. This is the rule we recommend for import_markdown_to_engrams:
{
"version": "1",
"default": "deny",
"tools": {
"import_markdown_to_engrams": {
"limits": [
{
"counter": "import_markdown_to_engrams_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_markdown_to_engrams 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.
Free to start. No card required.
Imports Engrams data from a directory of markdown files previously created by export_engrams_to_markdown. Reads from input_path (default: ./engrams_export/). WARNING: may overwrite existing data if IDs conflict. Use for restoring backups or migrating between workspaces. Precondition: files must follow the export format. Returns: {imported_path, entity_counts, errors}. It is categorised as a Write tool in the Engrams MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Engrams MCP server in PolicyLayer and add a rule for import_markdown_to_engrams: 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 Engrams. Nothing to install.
import_markdown_to_engrams 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_markdown_to_engrams 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_markdown_to_engrams. 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_markdown_to_engrams is provided by the Engrams MCP server (stevebrownlee/engrams). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Engrams, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
42 Engrams tools catalogued and risk-classified — across an index of 43,000+ MCP servers.