get_campaign_summary

Get campaign attribution breakdown by UTM campaign, source, medium, sessions, duration, and bounce rate.

Server KrystalView Analytics KrystalView/krystalview-mcp
Category Read
Risk class Low
Parameters 10 required

What get_campaign_summary does on KrystalView Analytics

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

ParameterTypeRequiredDescription
days integer Lookback period in days.

Parameters from the server's own tool schema.

Why get_campaign_summary needs a policy

This tool retrieves and aggregates existing campaign analytics data without modifying, executing code, or causing side effects. It is purely informational and safe for AI agent use.

From the tool's definition Tool name 'get_campaign_summary' and description 'Get campaign attribution breakdown' indicate data retrieval only. No modification, deletion, or execution keywords present.

Questions about get_campaign_summary

What does the get_campaign_summary tool do? +

Get campaign attribution breakdown by UTM campaign, source, medium, sessions, duration, and bounce rate. It is categorised as a Read tool in the KrystalView Analytics MCP Server, which means it retrieves data without modifying state.

What parameters does get_campaign_summary accept? +

get_campaign_summary accepts 1 parameter: days. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_campaign_summary? +

Register the KrystalView Analytics MCP server in PolicyLayer and add a rule for get_campaign_summary: 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.

What risk level is get_campaign_summary? +

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

Can I rate-limit get_campaign_summary? +

Yes. Add a rate_limit block to the get_campaign_summary 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_campaign_summary completely? +

Set action: deny in the PolicyLayer policy for get_campaign_summary. 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_campaign_summary? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.