get_flow
AI agents call get_flow to retrieve information from Klaviyo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' prefix is a standard REST convention for read-only retrieval operations. Sibling tools on this server include destructive operations (delete_profile), write operations (create_flow-like tools), and execute operations, establishing that 'get_' tools are likely read-only queries. Without a description, confidence is moderate (0.7), but the naming pattern strongly suggests data retrieval with no side effects.
From the tool's definition Tool name 'get_flow' suggests a retrieval operation. No description provided, but naming convention and context of a Klaviyo marketing automation server (where 'flow' refers to automated marketing workflows) indicate this retrieves flow data rather than…
Attacks that exploit this kind of access
get_flow. It is categorised as a Read tool in the Klaviyo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Klaviyo MCP Server MCP server in PolicyLayer and add a rule for get_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 Klaviyo MCP Server. Nothing to install.
get_flow 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 get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_flow is provided by the Klaviyo MCP Server MCP server (ivan-rivera-projects/klaviyo-mcp-server-enhanced). 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 →