Migrate Memory Bank files from camelCase to kebab-case naming convention
AI agents use migrate_file_naming 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 file metadata (naming) within a structured repository. While not creating new data (Write) nor permanently destroying it (Destructive), it reversibly transforms file naming conventions. The operation affects persistent storage and could impact downstream processes that depend on specific file names.
From the tool's definition Tool performs file renaming/migration operation on Memory Bank files, which modifies file names and potentially file system state.
Documented attack patterns abuse exactly the kind of access migrate_file_naming 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 migrate_file_naming:
{
"version": "1",
"default": "deny",
"tools": {
"migrate_file_naming": {
"limits": [
{
"counter": "migrate_file_naming_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}migrate_file_naming 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.
Migrate Memory Bank files from camelCase to kebab-case naming convention. 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 migrate_file_naming: 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.
migrate_file_naming 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 migrate_file_naming 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 migrate_file_naming. 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.
migrate_file_naming 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.