get_profitability
Revenue vs. costs, net profit, and margin over a period, optionally broken down by client. Answers "am I profitable this year?" or "which client is most profitable?"
This record as markdown: /tools/com-getsavitools-savi-tools/get-profitability.md
What get_profitability does on Savi Tools
AI agents call get_profitability to retrieve information from Savi Tools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
period | string | — | A 4-digit year, or this_year / last_year / this_quarter / last_quarter. Omit for the current fiscal year. |
byClient | boolean | — | Include a per-client profitability breakdown. |
Parameters from the server's own tool schema.
Why get_profitability is rated Low
This tool retrieves and aggregates historical financial data to answer profitability questions. It performs no writes, deletes, executions, or financial transactions. While the data is financial in nature, the tool itself is a passive query/reporting function with no side effects or ability to move money or change business state.
From the tool's definition Tool returns read-only financial metrics: 'Revenue vs. costs, net profit, and margin over a period' with optional breakdown 'by client.' All sibling tools follow a 'get_*' pattern indicating data retrieval.
Attacks that exploit this kind of access
The rule that runs get_profitability safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Savi Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_profitability, this is the rule to start with:
get_profitability is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Savi Tools, apply this rule, and every get_profitability call is checked against it from then on.
Questions about get_profitability
Revenue vs. costs, net profit, and margin over a period, optionally broken down by client. Answers "am I profitable this year?" or "which client is most profitable?". It is categorised as a Read tool in the Savi Tools MCP Server, which means it retrieves data without modifying state.
get_profitability accepts 2 parameters: period, byClient. The full parameter table on this page comes from the server's own tool schema.
Register the Savi Tools MCP server in PolicyLayer and add a rule for get_profitability: 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 Savi Tools. Nothing to install.
get_profitability 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_profitability 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_profitability. 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_profitability is provided by the Savi Tools MCP server (https://getsavitools.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Savi Tools, and thousands of servers like it.
This server
Across the catalogue