Calculate the percentage of subscriptions that cancelled within a date range. Uses subscription cancellation dates, not invoice gaps.
AI agents call get_churn_rate to retrieve information from Semantic BI MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and aggregates business metrics (churn rate) from existing subscription data. It performs a calculation on read-only data without creating, modifying, deleting, or executing external operations. The verb 'Calculate' combined with the metric retrieval pattern (consistent with sibling tools like get_arr, get_mrr, get_customer_count) confirms this is a Read operation.
From the tool's definition Tool description states 'Calculate the percentage of subscriptions that cancelled within a date range' — a retrieval and computation operation on historical subscription data with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Calculate the percentage of subscriptions that cancelled within a date range. Uses subscription cancellation dates, not invoice gaps. It is categorised as a Read tool in the Semantic BI MCP MCP Server, which means it retrieves data without modifying state.
Register the Semantic BI MCP server in PolicyLayer and add a rule for get_churn_rate: 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 Semantic BI MCP. Nothing to install.
get_churn_rate 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_churn_rate 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_churn_rate. 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_churn_rate is provided by the Semantic BI MCP server (lovrobubanic/semantic-bi-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 →