AI agents use import_file to create or update resources in Memory-Plus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memory-Plus environment.
The 'import_file' operation typically reads an external file and writes its contents into a system—in this case, the persistent memory store. This is a Write operation (creates or modifies data reversibly) rather than Read (which would only retrieve) or Execute (which would run arbitrary code).
From the tool's definition Tool name is 'import_file' with empty description. In the context of a RAG memory store server with sibling tools like 'record', 'record_memory', 'update', the 'import_file' tool likely creates or modifies data by importing external files into the memory…
Documented attack patterns abuse exactly the kind of access import_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memory-Plus, and nothing reaches the server without passing your rules. This is the rule we recommend for import_file:
{
"version": "1",
"default": "deny",
"tools": {
"import_file": {
"limits": [
{
"counter": "import_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_file 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.
import_file. It is categorised as a Write tool in the Memory-Plus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memory-Plus MCP server in PolicyLayer and add a rule for import_file: 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 Memory-Plus. Nothing to install.
import_file 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_file 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_file. 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_file is provided by the Memory-Plus MCP server (yuchen20/memory-plus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Memory-Plus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Memory-Plus tools catalogued and risk-classified — across an index of 42,500+ MCP servers.