New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

update_all_projects

Scan all registered project folders for activity. Refreshes CLAUDE.md for each.

SERVERMetis Public Health SOURCEsveritg/metis_ph
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sveritg-metis-ph/update-all-projects.md

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 update_all_projects is rated Medium

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.

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.

More on Metis Public Health, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Metis Public Health's. Pull the full record:

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.