AI agents call get_flows 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 convention for read-only operations that retrieve data without side effects. Given the broader context of the server managing marketing flows, segments, and campaigns, 'get_flows' most likely retrieves a list or details of existing flows. The absence of a description reduces confidence slightly, but the naming pattern is definitive. This poses minimal risk as it only queries data.
From the tool's definition Tool name 'get_flows' uses the 'get' prefix, indicating data retrieval. No description provided, but naming convention and context within a Klaviyo marketing automation platform strongly suggest querying existing flows rather than creating, modifying, or…
Documented attack patterns abuse exactly the kind of access get_flows gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Klaviyo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_flows:
{
"version": "1",
"default": "deny",
"tools": {
"get_flows": {}
}
}get_flows is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_flows. 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_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 Klaviyo MCP Server. Nothing to install.
get_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 get_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 get_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.
get_flows is provided by the Klaviyo MCP Server MCP server (mattcoatsworth/klaviyo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Klaviyo MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
41 Klaviyo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.