Delete the .first-run marker file to signal that the config wizard is complete.
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.
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.
Attacks that exploit this kind of access
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.
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.
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.
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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →