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

remove_first_run_marker

Delete the .first-run marker file to signal that the config wizard is complete.

SERVERMetis Public Health SOURCEsveritg/metis_ph
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sveritg-metis-ph/remove-first-run-marker.md

What remove_first_run_marker does on Metis Public Health

AI agents call remove_first_run_marker to permanently remove resources in Metis Public Health, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why remove_first_run_marker is rated Critical

This tool performs an irreversible deletion operation on a file (.first-run marker). Although the file is a configuration state marker with minimal consequence (not user data or critical application files), the action itself is destructive in nature—deletion cannot be undone and fits the Destructive category by definition.

From the tool's definition The tool description explicitly states 'Delete the .first-run marker file', using the verb 'delete' which indicates irreversible removal of data.

Questions about remove_first_run_marker

What does the remove_first_run_marker tool do? +

Delete the .first-run marker file to signal that the config wizard is complete. It is categorised as a Destructive tool in the Metis Public Health MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_first_run_marker? +

Register the Metis Public Health MCP server in PolicyLayer and add a rule for remove_first_run_marker: 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 remove_first_run_marker? +

remove_first_run_marker is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_first_run_marker? +

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

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

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