delete_data_trigger
Delete a data trigger permanently.
This record as markdown: /tools/sveritg-metis-ph/delete-data-trigger.md
What delete_data_trigger does on Metis Public Health
AI agents call delete_data_trigger 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 delete_data_trigger is rated Critical
This tool irreversibly removes data triggers from the system without recourse for recovery. In a research and knowledge management context, permanent deletion of configured data triggers could result in loss of indexing rules, automation workflows, or monitoring configurations that cannot be restored.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a data trigger permanently.' The word 'permanently' indicates irreversible deletion with no undo capability.
Attacks that exploit this kind of access
The rule that runs delete_data_trigger 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 delete_data_trigger, this is the rule to start with:
delete_data_trigger 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 delete_data_trigger call is checked against it from then on.
Questions about delete_data_trigger
Delete a data trigger permanently. 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 delete_data_trigger: 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.
delete_data_trigger 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 delete_data_trigger 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 delete_data_trigger. 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.
delete_data_trigger 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