update_all_projects · Metis Public Health MCP: Risk & Policy

WHAT IT DOES

What update_all_projects does on Metis Public Health

AI agents use update_all_projects to create or update resources in Metis Public Health — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metis Public Health environment.

WHY IT NEEDS A POLICY

Why update_all_projects needs a policy

This tool reads project metadata and writes updates to CLAUDE.md files across multiple projects. While it modifies files, the changes appear to be refreshes/regenerations of documentation rather than irreversible deletions, making it Write rather than Destructive.

From the tool's definition Tool description states it 'Refreshes CLAUDE.md for each' project, indicating modification of files. The verb 'scan' and 'refresh' imply reading and then writing back updated state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_all_projects Rate-limited

update_all_projects 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": {
    "update_all_projects": {
      "limits": [
        {
          "counter": "update_all_projects_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 Metis Public Health, so you can run agents against it safely.

FAQ

Questions about update_all_projects

What does the update_all_projects tool do? +

Scan all registered project folders for activity. Refreshes CLAUDE.md for each. It is categorised as a Write tool in the Metis Public Health MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_all_projects? +

Register the Metis Public Health MCP server in PolicyLayer and add a rule for update_all_projects: 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 Metis Public Health. Nothing to install.

What risk level is update_all_projects? +

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

Can I rate-limit update_all_projects? +

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

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

update_all_projects is provided by the Metis Public Health MCP server (sveritg/metis_ph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.