Paid invoice revenue grouped by plan for a given month. Uses the v_monthly_revenue view.
AI agents call get_revenue_by_plan 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 is a retrieval operation that queries aggregated business metrics. It has no side effects, cannot modify or delete data, and returns analytics information. Classification as Read is appropriate. Severity is low because misuse would only expose existing financial data, not alter it or trigger external actions.
From the tool's definition Tool retrieves 'Paid invoice revenue grouped by plan' from 'v_monthly_revenue view' — a query operation with no modification or deletion of data.
Attacks that exploit this kind of access
Paid invoice revenue grouped by plan for a given month. Uses the v_monthly_revenue view. 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_revenue_by_plan: 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_revenue_by_plan 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_revenue_by_plan 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_revenue_by_plan. 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_revenue_by_plan 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 →