Calculate Monthly Recurring Revenue (MRR) for a given month. Uses vetted SQL that excludes soft-deleted customers and counts only active/trialing subscriptions.
AI agents call get_mrr 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 retrieves and calculates a financial metric (MRR) from existing subscription data. It does not create, modify, delete, or move money; it reads and aggregates data using pre-vetted SQL. The blast radius of misuse is minimal—an AI could only retrieve incorrect or sensitive financial information, not alter systems or commit financial obligations. Categorized as Read with low severity.
From the tool's definition Tool name 'get_mrr' and description 'Calculate Monthly Recurring Revenue (MRR)' indicates a retrieval operation. Description explicitly states it 'uses vetted SQL' and performs calculation/aggregation rather than modification.
Attacks that exploit this kind of access
Calculate Monthly Recurring Revenue (MRR) for a given month. Uses vetted SQL that excludes soft-deleted customers and counts only active/trialing subscriptions. 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_mrr: 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_mrr 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_mrr 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_mrr. 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_mrr 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 →