trigger-progress

Send a progress/log notification to the client

SERVERFrontmcp SOURCEagentfront/frontmcp

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/frontmcp/trigger-progress.md

WHAT IT DOES

What trigger-progress does on Frontmcp

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

This tool executes an operation that sends data to the client and may trigger client-side effects (UI updates, logging, etc.). While it does not modify persistent data or run arbitrary code, it represents an executable action with side effects.

From the tool's definition "Send a progress/log notification to the client" — the tool triggers an action (sending a notification) whose effects depend on the notification content and client-side handling.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs trigger-progress safely

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

trigger-progress Rate-limited

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

FAQ

Questions about trigger-progress

What does the trigger-progress tool do? +

Send a progress/log notification to the client. It is categorised as a Execute tool in the Frontmcp 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-progress? +

Register the Front MCP server in PolicyLayer and add a rule for trigger-progress: 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 Frontmcp. Nothing to install.

What risk level is trigger-progress? +

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

Can I rate-limit trigger-progress? +

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

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

trigger-progress is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Front, and thousands of servers like it.

This server

All 206 Front 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 →