trigger

Trigger an immediate execution of a scheduled job (manual run).

SERVERNcp SOURCE@portel/ncp

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/io-github-portel-dev-ncp/trigger.md

WHAT IT DOES

What trigger does on Ncp

AI agents invoke trigger to trigger actions in Ncp. 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 trigger is rated High

This tool executes scheduled jobs on-demand, which is a form of code/operation execution. The severity is high because the blast radius depends on what the scheduled job performs - it could modify data, query systems, or trigger downstream processes.

From the tool's definition Tool description states 'Trigger an immediate execution of a scheduled job (manual run)' - directly triggers execution of external operations (scheduled jobs) whose effects depend on what the job does.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs trigger safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For trigger, this is the rule to start with:

trigger Rate-limited

trigger 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": {
    "trigger": {
      "limits": [
        {
          "counter": "trigger_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 Ncp, apply this rule, and every trigger call is checked against it from then on.

FAQ

Questions about trigger

What does the trigger tool do? +

Trigger an immediate execution of a scheduled job (manual run). It is categorised as a Execute tool in the Ncp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on trigger? +

Register the Ncp MCP server in PolicyLayer and add a rule for 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 Ncp. Nothing to install.

What risk level is trigger? +

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

Can I rate-limit trigger? +

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

How do I block trigger completely? +

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

What MCP server provides trigger? +

trigger is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp tools → High-risk tools on this server →

Across the catalogue

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 →