get_lists
AI agents call get_lists 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 tool retrieves or queries list data from Klaviyo without modification. The empty description lowers confidence slightly, but the naming convention ('get_') and context from sibling tools (which include destructive, write, and execute operations like 'delete_profile', 'create_list', 'create_event') clearly indicate this is a read operation with no side effects.
From the tool's definition Tool name 'get_lists' indicates a retrieval operation; sibling tools like 'create_list' and 'add_profiles_to_list' show this server manages lists, and 'get_' prefix is a standard pattern for read-only data fetching.
Attacks that exploit this kind of access
get_lists. 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_lists: 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_lists 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_lists 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_lists. 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_lists 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 →