create_workflow_template
Create a new custom workflow template the caller owns, so a multi-step pipeline can be built in conversation instead of by hand in the browser. Saves the same definition the web builder saves. The slug is derived from the name and is returned — use it with run_workflow. Legacy workflows run in de...
This record as markdown: /tools/com-meta-council-decision-intelligence/create-workflow-template.md
What create_workflow_template does on Meta Council
AI agents use create_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 | Yes | Template name, e.g. 'Competitor Teardown'. The saved slug is derived from this. |
tags | array | — | Optional tags for discovery. |
steps | array | Yes | The pipeline steps, in the order they will run. |
domain | string | — | Optional grouping domain, e.g. 'research'. Defaults to 'general'. |
description | string | — | Optional description of what the workflow does. |
Parameters from the server's own tool schema.
Why create_workflow_template is rated Medium
An AI agent can call create_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 (28 properties)
Attacks that exploit this kind of access
The rule that runs create_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 create_workflow_template, this is the rule to start with:
create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every create_workflow_template call is checked against it from then on.
Questions about create_workflow_template
Create a new custom workflow template the caller owns, so a multi-step pipeline can be built in conversation instead of by hand in the browser. Saves the same definition the web builder saves. The slug is derived from the name and is returned — use it with run_workflow. 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.
create_workflow_template accepts 5 parameters: name, tags, steps, domain, description. Required: name, steps. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for create_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.
create_workflow_template is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
More on Meta Council, and thousands of servers like it.
This server
Across the catalogue