Create a new multi-query workflow execution from template.
AI agents use create_workflow to create or update resources in Ai Analyst — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ai Analyst environment.
This tool creates new workflow objects that are stored and can be executed later. While creation is reversible (workflows can be deleted via delete_custom_metric or similar mechanisms), it modifies the system state by adding new workflow definitions. This is a Write operation rather than Read (it doesn't just query) or Execute (it creates the workflow definition, not executing arbitrary code directly).
From the tool's definition Tool description states 'Create a new multi-query workflow execution from template' — the word 'Create' indicates data creation.
Attacks that exploit this kind of access
Create a new multi-query workflow execution from template. It is categorised as a Write tool in the Ai Analyst MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ai Analyst MCP server in PolicyLayer and add a rule for create_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 Ai Analyst. Nothing to install.
create_workflow 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 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. 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 is provided by the Ai Analyst MCP server (sbdk-dev/local-ai-analyst). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →