AI agents call get_conversion_rate to retrieve information from Moneroo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a calculation and retrieves a metric (conversion rate) for analytics purposes. It does not create, modify, delete, or execute any actions. The sibling tools on this server include financial operations (create_payment_link, create_payout, create_recurring_payment) and destructive actions (export, delete), but this tool is purely informational retrieval, placing it in the Read category with low…
From the tool's definition The tool name is 'get_conversion_rate' and the description states it 'Calculate[s] the payment conversion rate for a period' — a read-only query that retrieves metrics data without modifying, executing external operations, or causing side effects.
Attacks that exploit this kind of access
Calculate the payment conversion rate for a period:. It is categorised as a Read tool in the Moneroo MCP Server, which means it retrieves data without modifying state.
Register the Moneroo MCP server in PolicyLayer and add a rule for get_conversion_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 Moneroo. Nothing to install.
get_conversion_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 get_conversion_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 get_conversion_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.
get_conversion_rate is provided by the Moneroo MCP server (moneroo-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 →