trigger_workflow_run · Rentalot MCP Server MCP

WHAT IT DOES

What trigger_workflow_run does on Rentalot MCP Server

AI agents invoke trigger_workflow_run to trigger actions in Rentalot MCP Server. 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.

WHY IT NEEDS A POLICY

Why trigger_workflow_run needs a policy

This tool triggers execution of workflows with asynchronous side effects. While the description labels it a 'Write operation,' the core function is to initiate and execute a workflow whose steps will run with effects that cannot be fully predicted without knowing the workflow definition. This fits Execute category (triggers external operations whose effects depend on arguments/configuration).

From the tool's definition Tool description explicitly states 'trigger a new run of a workflow' and 'workflow will execute its steps asynchronously.' The name 'trigger_workflow_run' indicates execution of an external operation whose effects depend on the workflow definition (unknown to…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trigger_workflow_run Rate-limited

trigger_workflow_run 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_workflow_run": {
      "limits": [
        {
          "counter": "trigger_workflow_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Rentalot MCP Server, so you can run agents against it safely.

FAQ

Questions about trigger_workflow_run

What does the trigger_workflow_run tool do? +

Use to trigger a new run of a workflow for a specific contact. Optionally scope it to a property. The workflow will execute its steps asynchronously. Write operation — requires Pro tier or higher. It is categorised as a Execute tool in the Rentalot MCP Server 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_workflow_run? +

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

What risk level is trigger_workflow_run? +

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

Can I rate-limit trigger_workflow_run? +

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

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

trigger_workflow_run is provided by the Rentalot MCP Server MCP server (rentalot-ai/rentalot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.