Create multiple flows in Directus at once. More efficient than creating flows one by one. Example: {flows: [{name:
AI agents use create_flows to create or update resources in Directus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Directus MCP Server environment.
This tool creates workflow automation flows in Directus. Creating flows is a Write operation (reversible creation of new records/configurations). While flows can trigger automated actions, the tool itself is creating configuration data, not executing arbitrary code. Severity is medium because misconfigured or malicious flows could trigger unintended automations, but the act of creation itself is reversible.
From the tool's definition "Create multiple flows in Directus at once. More efficient than creating flows one by one."
Attacks that exploit this kind of access
Create multiple flows in Directus at once. More efficient than creating flows one by one. Example: {flows: [{name:. It is categorised as a Write tool in the Directus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Directus MCP Server MCP server in PolicyLayer and add a rule for create_flows: 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 Directus MCP Server. Nothing to install.
create_flows 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_flows 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_flows. 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_flows is provided by the Directus MCP Server MCP server (skeyelab/directus-mcp-server). 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 →