update_flow · Directus MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_flow does on Directus MCP Server

AI agents use update_flow 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.

WHY IT NEEDS A POLICY

Why update_flow needs a policy

This tool modifies an existing flow (workflow automation) in Directus. It's a reversible modification operation — the flow can be updated again or reverted — so it falls under Write rather than Destructive. Severity is medium because modifying workflow automation logic could affect automated processes and data pipelines, but the action itself is reversible.

From the tool's definition Update an existing flow in Directus. Provide the flow ID and fields to update.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_flow Rate-limited

update_flow 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_flow": {
      "limits": [
        {
          "counter": "update_flow_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Directus MCP Server, so you can run agents against it safely.

FAQ

Questions about update_flow

What does the update_flow tool do? +

Update an existing flow in Directus. Provide the flow ID and fields to update. Example: {id:. 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.

How do I enforce a policy on update_flow? +

Register the Directus MCP Server MCP server in PolicyLayer and add a rule for update_flow: 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.

What risk level is update_flow? +

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

Can I rate-limit update_flow? +

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

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

update_flow 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.