update_flows · Directus MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_flows does on Directus MCP Server

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

WHY IT NEEDS A POLICY

Why update_flows needs a policy

This tool modifies existing flow records in Directus. Updating flows is a reversible write operation (flows can be updated again to restore prior state). It affects workflow automation configuration, which could have broader system impact if misused, but it does not irreversibly delete or destroy data, justifying 'Write' at medium severity.

From the tool's definition Update multiple flows in Directus at once. Each flow must include an id field.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_flows Rate-limited

update_flows 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_flows": {
      "limits": [
        {
          "counter": "update_flows_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_flows

What does the update_flows tool do? +

Update multiple flows in Directus at once. Each flow must include an id field. Example: {flows: [{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_flows? +

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

What risk level is update_flows? +

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

Can I rate-limit update_flows? +

Yes. Add a rate_limit block to the update_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.

How do I block update_flows completely? +

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

What MCP server provides update_flows? +

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

// THE FULL RECORD

update_flows is one line of Directus MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →