refresh_project_map · Project Context Map MCP: Risk & Policy

WHAT IT DOES

What refresh_project_map does on Project Context Map

AI agents use refresh_project_map to create or update resources in Project Context Map — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Project Context Map environment.

WHY IT NEEDS A POLICY

Why refresh_project_map needs a policy

This tool overwrites two specific files (.project-map.json and .project-map.md) with freshly generated content. While it does overwrite existing files, it is regenerating structured project metadata that can be recreated, making it a Write operation rather than Destructive. Misuse could corrupt project map files used by AI agents, but the files are regenerable from source.

From the tool's definition Regenerate .project-map.json and .project-map.md for the current repository

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

refresh_project_map Rate-limited

refresh_project_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": {
    "refresh_project_map": {
      "limits": [
        {
          "counter": "refresh_project_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 Project Context Map, so you can run agents against it safely.

FAQ

Questions about refresh_project_map

What does the refresh_project_map tool do? +

Regenerate .project-map.json and .project-map.md for the current repository. It is categorised as a Write tool in the Project Context Map MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on refresh_project_map? +

Register the Project Context Map MCP server in PolicyLayer and add a rule for refresh_project_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 Project Context Map. Nothing to install.

What risk level is refresh_project_map? +

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

Can I rate-limit refresh_project_map? +

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

Set action: deny in the PolicyLayer policy for refresh_project_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 refresh_project_map? +

refresh_project_map is provided by the Project Context Map MCP server (tamojit-123/project-context-map-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

refresh_project_map is one line of Project Context Map's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →