list_data_triggers
List all data automation triggers with their status.
This record as markdown: /tools/sveritg-metis-ph/list-data-triggers.md
What list_data_triggers does on Metis Public Health
AI agents call list_data_triggers to retrieve information from Metis Public Health without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_data_triggers is rated Low
This tool performs a passive information retrieval operation (list/query) with no side effects. It retrieves metadata about triggers and their states but does not create, modify, delete, or execute any triggers. The blast radius of misuse is minimal—exposure of trigger metadata could inform an adversary about system automation, but cannot directly cause harm. This is a classic Read operation.
From the tool's definition Tool name 'list_data_triggers' combined with description 'List all data automation triggers with their status' indicates a retrieval/query operation that enumerates existing automation triggers without modifying, executing, or deleting them.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs list_data_triggers 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 list_data_triggers, this is the rule to start with:
list_data_triggers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Metis Public Health, apply this rule, and every list_data_triggers call is checked against it from then on.
Questions about list_data_triggers
List all data automation triggers with their status. It is categorised as a Read tool in the Metis Public Health MCP Server, which means it retrieves data without modifying state.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for list_data_triggers: 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.
list_data_triggers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_data_triggers 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 list_data_triggers. 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.
list_data_triggers 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.
This server
Across the catalogue