Get paid campaign spend, clicks, sessions, attributed conversions, and ROAS where ad data is connected.
AI agents call get_campaign_roas to retrieve information from KrystalView Analytics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
days | integer | — | Lookback period in days. |
Parameters from the server's own tool schema.
The tool is a read-only query that retrieves existing campaign performance metrics and calculated ROAS (return on ad spend). It has no capability to modify, delete, or execute operations.
From the tool's definition Tool retrieves analytics data ('Get paid campaign spend, clicks, sessions, attributed conversions, and ROAS') with no modification verbs; performs data aggregation and query only.
Attacks that exploit this kind of access
Get paid campaign spend, clicks, sessions, attributed conversions, and ROAS where ad data is connected. It is categorised as a Read tool in the KrystalView Analytics MCP Server, which means it retrieves data without modifying state.
get_campaign_roas accepts 1 parameter: days. The full parameter table on this page comes from the server's own tool schema.
Register the KrystalView Analytics MCP server in PolicyLayer and add a rule for get_campaign_roas: 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 KrystalView Analytics. Nothing to install.
get_campaign_roas 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_roas 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_roas. 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_roas is provided by the KrystalView Analytics MCP server (KrystalView/krystalview-mcp). 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 →