get_revenue_summary

Revenue breakdown by period, type, and practice. Includes MRR from recurring billing, checkout revenue, and invoice payments.

SERVERBusinys SOURCE@businys/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/app-businys-mcp-server/get-revenue-summary.md

WHAT IT DOES

What get_revenue_summary does on Businys

AI agents call get_revenue_summary to retrieve information from Businys without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_revenue_summary is rated Low

This tool retrieves and summarizes financial data (MRR, checkout revenue, invoice payments) but does not move money, create financial obligations, or modify data. It is a read-only reporting function with no side effects. Blast radius is minimal—an agent misusing this would only access financial visibility data, not execute transactions or cause destructive changes.

From the tool's definition Tool name 'get_revenue_summary' and description 'Revenue breakdown by period, type, and practice' indicate a retrieval/query operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_revenue_summary safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_revenue_summary, this is the rule to start with:

get_revenue_summary Allowed

get_revenue_summary is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_revenue_summary": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Businys, apply this rule, and every get_revenue_summary call is checked against it from then on.

FAQ

Questions about get_revenue_summary

What does the get_revenue_summary tool do? +

Revenue breakdown by period, type, and practice. Includes MRR from recurring billing, checkout revenue, and invoice payments. It is categorised as a Read tool in the Businys MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_revenue_summary? +

Register the Businys MCP server in PolicyLayer and add a rule for get_revenue_summary: 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 Businys. Nothing to install.

What risk level is get_revenue_summary? +

get_revenue_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_revenue_summary? +

Yes. Add a rate_limit block to the get_revenue_summary 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.

How do I block get_revenue_summary completely? +

Set action: deny in the PolicyLayer policy for get_revenue_summary. 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.

What MCP server provides get_revenue_summary? +

get_revenue_summary is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Businys, and thousands of servers like it.

This server

All 248 Businys tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →