run_trigger_now

Manually execute a data trigger right now.

SERVERMetis Public Health SOURCEsveritg/metis_ph

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sveritg-metis-ph/run-trigger-now.md

WHAT IT DOES

What run_trigger_now does on Metis Public Health

AI agents invoke run_trigger_now to trigger actions in Metis Public Health. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why run_trigger_now is rated High

This tool fits the Execute category because it runs a trigger—an automated operation whose effects depend on what the trigger is configured to do. While the exact consequences are context-dependent (and could potentially be Write, Destructive, or other outcomes), the tool itself performs an execution action.

From the tool's definition The tool is described as 'Manually execute a data trigger right now.' The verb 'execute' and the concept of 'trigger' indicate that this tool runs or invokes some operation or automation, rather than simply reading or writing data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_trigger_now 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 run_trigger_now, this is the rule to start with:

run_trigger_now Rate-limited

run_trigger_now stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_trigger_now": {
      "limits": [
        {
          "counter": "run_trigger_now_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Metis Public Health, apply this rule, and every run_trigger_now call is checked against it from then on.

FAQ

Questions about run_trigger_now

What does the run_trigger_now tool do? +

Manually execute a data trigger right now. It is categorised as a Execute tool in the Metis Public Health MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_trigger_now? +

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

run_trigger_now is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_trigger_now? +

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

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

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

KEEP EXPLORING

More on Metis Public Health, and thousands of servers like it.

This server

All 277 Metis Public Health tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP →qt_trigger_action on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →