Compare total paid revenue between two months and return NRR as a percentage (comparison / base × 100).
AI agents call get_net_revenue_retention 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 computes a financial metric (Net Revenue Retention) from existing data without creating, modifying, deleting, or executing arbitrary operations. It performs a straightforward analytical calculation over historical business data.
From the tool's definition Tool description indicates it 'Compare[s] total paid revenue between two months and return[s] NRR as a percentage' — a read-only retrieval and calculation operation.
Attacks that exploit this kind of access
Compare total paid revenue between two months and return NRR as a percentage (comparison / base × 100). 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_net_revenue_retention: 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_net_revenue_retention 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_net_revenue_retention 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_net_revenue_retention. 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_net_revenue_retention 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 →