generate_all_folder_maps · MCP Memory Server MCP

WHAT IT DOES

What generate_all_folder_maps does on MCP Memory Server

AI agents use generate_all_folder_maps to create or update resources in MCP Memory Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Memory Server environment.

WHY IT NEEDS A POLICY

Why generate_all_folder_maps needs a policy

This tool creates new files (_map.md) or overwrites existing ones across multiple project folders. While reversible (files can be deleted or regenerated), it modifies the project structure and creates output that persists. This is a Write rather than Read operation because it generates/creates artifacts.

From the tool's definition generate_all_folder_maps produces (_map.md files for all folders in the project), creating/modifying files across the project. The description explicitly states generation of files, which is a write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_all_folder_maps Rate-limited

generate_all_folder_maps 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_all_folder_maps": {
      "limits": [
        {
          "counter": "generate_all_folder_maps_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Memory Server, so you can run agents against it safely.

FAQ

Questions about generate_all_folder_maps

What does the generate_all_folder_maps tool do? +

Generate _map.md files for all folders in the project. It is categorised as a Write tool in the MCP Memory Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_all_folder_maps? +

Register the MCP Memory Server MCP server in PolicyLayer and add a rule for generate_all_folder_maps: 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 MCP Memory Server. Nothing to install.

What risk level is generate_all_folder_maps? +

generate_all_folder_maps is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_all_folder_maps? +

Yes. Add a rate_limit block to the generate_all_folder_maps 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.

How do I block generate_all_folder_maps completely? +

Set action: deny in the PolicyLayer policy for generate_all_folder_maps. 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.

What MCP server provides generate_all_folder_maps? +

generate_all_folder_maps is provided by the MCP Memory Server MCP server (keleshteri/mcp-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.