get_usd_to_cop_trm_by_date_range
AI agents call get_usd_to_cop_trm_by_date_range 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.
The tool appears to retrieve historical USD-to-COP exchange rate data (TRM = Tasa Representativa del Mercado) for a specified date range. It follows the naming pattern of other read-only data retrieval tools on the server. Although the description is empty, the consistent naming convention and context of sibling tools strongly indicate this is a data query operation with no side effects.
From the tool's definition Tool name 'get_usd_to_cop_trm_by_date_range' indicates a retrieval operation (get); sibling tools include 'get_inflation_data', 'get_usd_to_cop_trm_by_date', and 'get_usd_to_cop_trm_historical_data' which are all read operations that fetch financial/economic…
Documented attack patterns abuse exactly the kind of access get_usd_to_cop_trm_by_date_range 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_by_date_range:
{
"version": "1",
"default": "deny",
"tools": {
"get_usd_to_cop_trm_by_date_range": {}
}
}get_usd_to_cop_trm_by_date_range 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_by_date_range. 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_by_date_range: 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_by_date_range 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_by_date_range 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_by_date_range. 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_by_date_range 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.