List conversion funnels defined for this site.
AI agents call get_funnels 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.
This tool retrieves and enumerates existing conversion funnel configurations without modifying, executing, or deleting any data. It is a straightforward data retrieval operation consistent with analytics read access. The low severity reflects minimal risk even if accessed by an unauthorized agent, as it only exposes funnel definitions without enabling modification or execution.
From the tool's definition Tool name 'get_funnels' and description 'List conversion funnels defined for this site' indicate a retrieval operation. The verb 'List' explicitly denotes a read-only query with no side effects.
Attacks that exploit this kind of access
List conversion funnels defined for this site. It is categorised as a Read tool in the KrystalView Analytics MCP Server, which means it retrieves data without modifying state.
Register the KrystalView Analytics MCP server in PolicyLayer and add a rule for get_funnels: 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_funnels 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_funnels 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_funnels. 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_funnels 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 →