generate_folder_map · MCP Memory Server MCP: Risk & Policy

WHAT IT DOES

What generate_folder_map does on MCP Memory Server

AI agents use generate_folder_map 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_folder_map needs a policy

This tool creates or modifies documentation files (_map.md) in a folder structure. It is a Write operation because it produces or updates data with reversible effects. The severity is low because generating folder maps is a benign documentation activity with no risk of data loss, financial impact, or system compromise.

From the tool's definition Tool description states it will 'Generate or update a _map.md file', which explicitly indicates creating or modifying data. The action is reversible—a _map.md file can be edited or deleted later.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_folder_map Rate-limited

generate_folder_map 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_folder_map": {
      "limits": [
        {
          "counter": "generate_folder_map_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_folder_map

What does the generate_folder_map tool do? +

Generate or update a _map.md file for a specific folder. 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_folder_map? +

Register the MCP Memory Server MCP server in PolicyLayer and add a rule for generate_folder_map: 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_folder_map? +

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

Can I rate-limit generate_folder_map? +

Yes. Add a rate_limit block to the generate_folder_map 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_folder_map completely? +

Set action: deny in the PolicyLayer policy for generate_folder_map. 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_folder_map? +

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