update_workflow_template

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

Medium RISK CLASS

Category Write

Parameters 71 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/update-workflow-template.md

WHAT IT DOES

What update_workflow_template does on Meta Council

AI agents use update_workflow_template to create or update resources in Meta Council, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Council environment.

Parameter	Type	Required	Description
`name`	string	—	Template name after the update.
`slug`	string	Yes	Slug of the template to replace, from list_workflows.
`tags`	array	—	Tags after the update.
`steps`	array	—	The complete step list after the update, in run order.
`domain`	string	—	Grouping domain after the update.
`description`	string	—	Description after the update.
`expected_template_fingerprint`	string	—	Optional. The definition fingerprint you last saw for this template, returned by update_workflow_template when it last succeeded. Supply it and the write refuse

Parameters from the server's own tool schema.

RISK

Why update_workflow_template is rated Medium

An AI agent can call update_workflow_template faster than any human can review: one bad instruction and it creates or modifies resources in Meta Council by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (30 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_workflow_template 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 update_workflow_template, this is the rule to start with:

update_workflow_template Rate-limited

update_workflow_template stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_workflow_template": {
      "limits": [
        {
          "counter": "update_workflow_template_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 update_workflow_template call is checked against it from then on.

FAQ

Questions about update_workflow_template

What does the update_workflow_template tool do? +

Replace an existing custom workflow template's definition. This is a full replacement, not a patch: supply name and steps as you want them to end up, because anything omitted is not carried over. Built-in templates are read-only, and only the template's owner may change it. Legacy workflows run in dependency order; steps ready together share one bounded parallel layer, while no depends_on keeps authored list order. Explicitly routed workflows use next_step and bounded quality-gate transitions and cannot mix those fields with depends_on. Requires authentication and the workflows:write scope. It is categorised as a Write tool in the Meta Council MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_workflow_template accept? +

update_workflow_template accepts 7 parameters: name, slug, tags, steps, domain, description, expected_template_fingerprint. Required: slug. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_workflow_template? +

Register the Meta Council MCP server in PolicyLayer and add a rule for update_workflow_template: 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 update_workflow_template? +

update_workflow_template is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_workflow_template? +

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

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

update_workflow_template 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 →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →