AI agents call get_currencies to retrieve information from Currency Converter MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves reference data (available currencies) with no side effects. It is a straightforward data query operation with minimal blast radius if misused—an AI agent listing currencies poses no harm. Low severity and high confidence despite the empty description, given the clear naming convention and server purpose.
From the tool's definition Tool name is 'get_currencies' and sibling tools indicate this server provides 'currency conversion and exchange rate data' with abilities to 'list available currencies.' The tool description is empty, but the name and context strongly suggest it retrieves a…
Documented attack patterns abuse exactly the kind of access get_currencies gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Currency Converter MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_currencies:
{
"version": "1",
"default": "deny",
"tools": {
"get_currencies": {}
}
}get_currencies 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.
get_currencies. It is categorised as a Read tool in the Currency Converter MCP MCP Server, which means it retrieves data without modifying state.
Register the Currency Converter MCP server in PolicyLayer and add a rule for get_currencies: 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 Currency Converter MCP. Nothing to install.
get_currencies 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_currencies 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_currencies. 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_currencies is provided by the Currency Converter MCP server (wesbos/currency-conversion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Currency Converter MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 Currency Converter MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.