start_external_workflow

SERVERMeta Council SOURCEhttps://meta-council.com/mcp

High RISK CLASS

Category Execute

Parameters 33 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-meta-council-decision-intelligence/start-external-workflow.md

WHAT IT DOES

What start_external_workflow does on Meta Council

AI agents invoke start_external_workflow to trigger actions in Meta Council. 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.

Parameter	Type	Required
`query`	string	Yes
`workflow`	enum	Yes
`request_id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why start_external_workflow is rated High

start_external_workflow triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs start_external_workflow safely

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

start_external_workflow Rate-limited

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

FAQ

Questions about start_external_workflow

What does the start_external_workflow tool do? +

Start a caller-executed sales evidence draft. Returns frozen instructions for your agent to execute. No server model call, tools or sending. Reuse request_id only with identical inputs. Results are caller attestations, not verified provider usage. Requires workflows:run. It is categorised as a Execute tool in the Meta Council MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does start_external_workflow accept? +

start_external_workflow accepts 3 parameters: query, workflow, request_id. Required: query, workflow, request_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on start_external_workflow? +

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

What risk level is start_external_workflow? +

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

Can I rate-limit start_external_workflow? +

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

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

start_external_workflow is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meta Council, and thousands of servers like it.

This server

All 280 Meta Council tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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