List all flows that exist in Directus. Supports filtering, sorting, pagination, and search. Example: {filter: {
AI agents call list_flows to retrieve information from Directus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about existing Directus flows without creating, modifying, deleting, or executing anything. It is a straightforward data retrieval operation that poses minimal security risk if misused by an AI agent, as it only exposes metadata about workflows without triggering them or changing state.
From the tool's definition Tool name is 'list_flows' and description states 'List all flows that exist in Directus. Supports filtering, sorting, pagination, and search.' The verb 'List' and the capabilities described (filtering, sorting, pagination, search) are all read-only query…
Attacks that exploit this kind of access
List all flows that exist in Directus. Supports filtering, sorting, pagination, and search. Example: {filter: {. It is categorised as a Read tool in the Directus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Directus MCP Server MCP server in PolicyLayer and add a rule for list_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.
list_flows is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_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 list_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.
list_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 →