remove_tracked_file
A destructive tool on the Metis Public Health MCP server.
This record as markdown: /tools/sveritg-metis-ph/remove-tracked-file.md
What remove_tracked_file does on Metis Public Health
AI agents call remove_tracked_file 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_tracked_file is rated Critical
The tool removes tracked files, which is an irreversible operation that deletes data from the user's indexed library or tracking system. No description is provided, lowering confidence slightly, but the naming convention strongly suggests permanent deletion rather than reversible modification.
From the tool's definition Tool name is 'remove_tracked_file' — the verb 'remove' indicates deletion or irreversible removal of a tracked file from the system.
Attacks that exploit this kind of access
The rule that runs remove_tracked_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Metis Public Health, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_tracked_file, this is the rule to start with:
remove_tracked_file is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Metis Public Health, apply this rule, and every remove_tracked_file call is checked against it from then on.
Questions about remove_tracked_file
remove_tracked_file is a destructive tool on the Metis Public Health MCP server. 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_tracked_file: 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_tracked_file 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_tracked_file 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_tracked_file. 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_tracked_file 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.
Across the catalogue