get_campaign_recipient_estimation
AI agents call get_campaign_recipient_estimation 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.
This tool appears to retrieve or estimate campaign recipient metrics based on the 'get_' prefix and the nature of 'recipient_estimation' as a read operation. It queries campaign data to provide estimates rather than modifying, executing, or deleting anything.
From the tool's definition Tool name 'get_campaign_recipient_estimation' indicates retrieval/estimation of campaign recipient data with 'get' prefix. The empty description is uninformative, but the naming convention strongly suggests a query operation without side effects.
Attacks that exploit this kind of access
get_campaign_recipient_estimation. 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_campaign_recipient_estimation: 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_campaign_recipient_estimation 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_campaign_recipient_estimation 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_campaign_recipient_estimation. 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_campaign_recipient_estimation 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 →