effective_rate
Effective Rate (APR <-> APY) — Convert a nominal rate to effective annual yield, or back, at any compounding frequency.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/effective-rate.md
What effective_rate does on Gateway
AI agents call effective_rate 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 |
|---|---|---|---|
apr | number | — | Nominal annual rate as a decimal (to_apy) |
apy | number | — | Effective annual yield as a decimal (to_apr) |
mode | string | — | Direction |
periods | number | — | Compounding periods per year, or 'continuous' (default 12) |
Parameters from the server's own tool schema.
Why effective_rate is rated Low
This tool retrieves and computes financial rate information without creating, modifying, deleting, or moving money. It is a calculator that transforms input rates into equivalent forms. While it operates in a financial domain, it does not execute financial transactions, commit obligations, or alter any state. The conversion is reversible and deterministic.
From the tool's definition Tool performs rate conversion calculations (APR <-> APY) with no side effects, data modification, or external state changes. Description states 'Convert... at any compounding frequency' — a pure computational/query function.
Attacks that exploit this kind of access
The rule that runs effective_rate 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 effective_rate, this is the rule to start with:
effective_rate 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 effective_rate call is checked against it from then on.
Questions about effective_rate
Effective Rate (APR <-> APY) — Convert a nominal rate to effective annual yield, or back, at any compounding frequency. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
effective_rate accepts 4 parameters: apr, apy, mode, periods. 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 effective_rate: 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.
effective_rate 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 effective_rate 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 effective_rate. 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.
effective_rate 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