AI agents use set_memory_bank_path to create or update resources in Memory Bank MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memory Bank MCP environment.
This tool modifies system configuration by changing where the Memory Bank points to, which is a reversible write operation. While it doesn't create or delete data, it alters stored configuration state. Severity is medium because misconfiguration could disrupt the system's ability to access memory correctly or cause the system to reference an unintended path, but the operation itself is reversible.
From the tool's definition Tool name 'set_memory_bank_path' and description 'Set a custom path for the Memory Bank' indicate modification of configuration state. The word 'Set' explicitly indicates a write operation that changes the memory bank's path setting.
Documented attack patterns abuse exactly the kind of access set_memory_bank_path gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memory Bank MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for set_memory_bank_path:
{
"version": "1",
"default": "deny",
"tools": {
"set_memory_bank_path": {
"limits": [
{
"counter": "set_memory_bank_path_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_memory_bank_path 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.
Set a custom path for the Memory Bank. It is categorised as a Write tool in the Memory Bank MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memory Bank MCP server in PolicyLayer and add a rule for set_memory_bank_path: 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 Bank MCP. Nothing to install.
set_memory_bank_path 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 set_memory_bank_path 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 set_memory_bank_path. 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.
set_memory_bank_path is provided by the Memory Bank MCP server (movibe/memory-bank-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memory Bank MCP, 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.
15 Memory Bank MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.