roi
ROI & Annualized Return Calculator — Return on investment, gain and (with a holding period) annualized ROI.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/roi.md
What roi does on Gateway
AI agents call roi to retrieve information from Gateway 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 |
|---|---|---|---|
years | number | — | Holding period in years (for annualized ROI) |
final_value | number | Yes | Final/exit value in USD |
initial_investment | number | Yes | Initial investment in USD |
Parameters from the server's own tool schema.
Why roi is rated Low
This tool performs mathematical calculations on investment data to derive return metrics. It takes inputs (investment amount, gain, holding period) and computes outputs (ROI percentage, annualized return) with no side effects, data modification, or external state changes. No money moves, no records are created or deleted, and no external systems are triggered.
From the tool's definition Tool name 'roi' and description 'ROI & Annualized Return Calculator — Return on investment, gain and (with a holding period) annualized ROI' indicate a calculation/analysis function that reads input parameters and returns computed financial metrics.
Attacks that exploit this kind of access
The rule that runs roi safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For roi, this is the rule to start with:
roi 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 Gateway, apply this rule, and every roi call is checked against it from then on.
Questions about roi
ROI & Annualized Return Calculator — Return on investment, gain and (with a holding period) annualized ROI. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
roi accepts 3 parameters: years, final_value, initial_investment. Required: final_value, initial_investment. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for roi: 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 Gateway. Nothing to install.
roi 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 roi 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 roi. 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.
roi is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue