run_instance_trigger

Manually run one configured instance trigger now. This can create tasks, add knowledge, or sync a granted connector folder.

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/run-instance-trigger.md

WHAT IT DOES

What run_instance_trigger does on ProAgentStore

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

Executes external operations with effects dependent on trigger configuration; high blast radius from misuse.

From the tool's definition Manually run configured instance trigger; create tasks, add knowledge, sync connector folder

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_instance_trigger safely

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

run_instance_trigger Rate-limited

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

FAQ

Questions about run_instance_trigger

What does the run_instance_trigger tool do? +

Manually run one configured instance trigger now. This can create tasks, add knowledge, or sync a granted connector folder. It is categorised as a Execute tool in the ProAgentStore 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_instance_trigger? +

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

What risk level is run_instance_trigger? +

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

Can I rate-limit run_instance_trigger? +

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

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

run_instance_trigger is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ProAgentStore, and thousands of servers like it.

This server

All 243 ProAgentStore tools → High-risk tools on this server →

Across the catalogue

editor_run_template on 010 Editor →run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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