Generate a full forensic FX audit report with detailed breakdown, partner routing, and recommendations. Requires a valid Bearer API token from the iPayX dashboard.
AI agents call full_forensic_report to retrieve information from iPayX FX Audit — Hidden Bank Fee Detector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
amount | number | — | |
bank_rate | number | — | |
currency_to | string | — | |
company_name | string | — | Optional company name for the report |
currency_from | string | — |
Parameters from the server's own tool schema.
This tool retrieves and analyzes transaction data to produce a report—a classic Read operation. While the server context mentions 'FX fees' and 'bank transfers' (suggesting financial domain), the tool itself does not move money, execute trades, modify records, or commit financial obligations.
From the tool's definition The tool 'full_forensic_report' generates a report with 'detailed breakdown, partner routing, and recommendations.' The verb 'Generate' here means producing an analysis or output based on existing data, not modifying, executing code, or moving money.
Documented attack patterns abuse exactly the kind of access full_forensic_report gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and iPayX FX Audit — Hidden Bank Fee Detector, and nothing reaches the server without passing your rules. This is the rule we recommend for full_forensic_report:
{
"version": "1",
"default": "deny",
"tools": {
"full_forensic_report": {}
}
}full_forensic_report is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate a full forensic FX audit report with detailed breakdown, partner routing, and recommendations. Requires a valid Bearer API token from the iPayX dashboard. It is categorised as a Read tool in the iPayX FX Audit — Hidden Bank Fee Detector MCP Server, which means it retrieves data without modifying state.
full_forensic_report accepts 5 parameters: amount, bank_rate, currency_to, company_name, currency_from. The full parameter table on this page comes from the server's own tool schema.
Register the iPayX FX Audit — Hidden Bank Fee Detector MCP server in PolicyLayer and add a rule for full_forensic_report: 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 iPayX FX Audit — Hidden Bank Fee Detector. Nothing to install.
full_forensic_report 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 full_forensic_report 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 full_forensic_report. 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.
full_forensic_report is provided by the iPayX FX Audit — Hidden Bank Fee Detector MCP server (ybolduc/ipayx-fx-audit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from iPayX FX Audit — Hidden Bank Fee Detector, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 iPayX FX Audit — Hidden Bank Fee Detector tools catalogued and risk-classified — across an index of 43,000+ MCP servers.