Create a conversion funnel to track user journey through multiple steps.
AI agents use savri_create_funnel to create or update resources in Savri Analytics MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Savri Analytics MCP Server environment.
This tool creates new analytics configurations (conversion funnels) which modifies the analytics setup reversibly. It is not destructive since funnels can be deleted (evidenced by sibling tool savri_delete_funnel), and it does not execute arbitrary code or handle financial transactions.
From the tool's definition Tool name 'savri_create_funnel' and description 'Create a conversion funnel' explicitly indicates data creation.
Attacks that exploit this kind of access
Create a conversion funnel to track user journey through multiple steps. It is categorised as a Write tool in the Savri Analytics MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Savri Analytics MCP Server MCP server in PolicyLayer and add a rule for savri_create_funnel: 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 Savri Analytics MCP Server. Nothing to install.
savri_create_funnel is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the savri_create_funnel 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 savri_create_funnel. 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.
savri_create_funnel is provided by the Savri Analytics MCP Server MCP server (savri-io/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 →