Low Risk

get_metrics

get_metrics

How to control get_metrics ↓

What get_metrics does on Klaviyo MCP Server

AI agents call get_metrics 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.

Low Risk

Why get_metrics needs a policy

The 'get_' prefix is a strong indicator of a read-only retrieval operation. Within the Klaviyo platform context (campaigns, flows, profiles), metrics typically refer to analytics data like open rates, click rates, or engagement statistics. Retrieving this data has no side effects and does not modify, delete, execute code, or commit financial transactions.

From the tool's definition Tool name 'get_metrics' indicates retrieval of metrics data. The Klaviyo context (marketing/email platform) suggests this queries analytics or performance data without modification. No description provided, lowering confidence slightly.

Documented attack patterns abuse exactly the kind of access get_metrics gives an agent:

How to control get_metrics

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_metrics:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_metrics": {}
  }
}

get_metrics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Klaviyo MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_metrics

What does the get_metrics tool do? +

get_metrics. It is categorised as a Read tool in the Klaviyo MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_metrics? +

Register the Klaviyo MCP Server MCP server in PolicyLayer and add a rule for get_metrics: 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.

What risk level is get_metrics? +

get_metrics is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_metrics? +

Yes. Add a rate_limit block to the get_metrics 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.

How do I block get_metrics completely? +

Set action: deny in the PolicyLayer policy for get_metrics. 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.

What MCP server provides get_metrics? +

get_metrics 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.

Enforce policy on every Klaviyo MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.