get_usd_to_cop_trm_historical_data
AI agents call get_usd_to_cop_trm_historical_data to retrieve information from Banrepco without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical financial data (exchange rates) but does not execute transactions, modify data, delete data, or move money. It is a read-only query operation. Confidence is slightly reduced because the description is empty, but the function name is sufficiently clear and consistent with sibling tools that provide inflation and exchange rate lookups without write/execute capabilities.
From the tool's definition Tool name 'get_usd_to_cop_trm_historical_data' indicates retrieval of historical USD-to-COP exchange rate data (TRM = Tasa de Cambio Representativa del Mercado).
Documented attack patterns abuse exactly the kind of access get_usd_to_cop_trm_historical_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Banrepco, and nothing reaches the server without passing your rules. This is the rule we recommend for get_usd_to_cop_trm_historical_data:
{
"version": "1",
"default": "deny",
"tools": {
"get_usd_to_cop_trm_historical_data": {}
}
}get_usd_to_cop_trm_historical_data 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_usd_to_cop_trm_historical_data. It is categorised as a Read tool in the Banrepco MCP Server, which means it retrieves data without modifying state.
Register the Banrepco MCP server in PolicyLayer and add a rule for get_usd_to_cop_trm_historical_data: 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 Banrepco. Nothing to install.
get_usd_to_cop_trm_historical_data 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_usd_to_cop_trm_historical_data 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_usd_to_cop_trm_historical_data. 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_usd_to_cop_trm_historical_data is provided by the Banrepco MCP server (kevyder/banrepco_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Banrepco, 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.
6 Banrepco tools catalogued and risk-classified — across an index of 43,000+ MCP servers.