List sessions attributed to a specific marketing campaign.
AI agents call get_campaign_sessions 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 |
|---|---|---|---|
limit | integer | — | Maximum results to return. |
offset | integer | — | Pagination offset. |
campaign | string | Yes | UTM campaign name. |
Parameters from the server's own tool schema.
This tool retrieves and lists session data attributed to marketing campaigns. It performs a query operation with no side effects—it does not create, modify, delete, execute code, or commit financial transactions. The 'get_' prefix and analytics context confirm it is a read-only data retrieval operation with low risk of misuse.
From the tool's definition Tool name 'get_campaign_sessions' and description 'List sessions' indicate a retrieval operation. All sibling tools (get_anomalies, get_campaign_roas, get_errors, get_live_visitors, etc.) follow the 'get_*' pattern and are read-only analytics queries with no…
Attacks that exploit this kind of access
List sessions attributed to a specific marketing campaign. It is categorised as a Read tool in the KrystalView Analytics MCP Server, which means it retrieves data without modifying state.
get_campaign_sessions accepts 3 parameters: limit, offset, campaign. Required: campaign. 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_sessions: 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_sessions 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_sessions 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_sessions. 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_sessions 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 →