Validates a Mexican CLABE (Clave Bancaria Estandarizada) — the 18-digit standardized bank account number used for electronic transfers in Mexico, as defined by BANXICO (Banco de México). Applies the official weighted modulo-10 checksum algorithm (weights: 3,7,1 repeating). Returns { valid: boolea...
AI agents call validate_clabe_mx to retrieve information from Mcp Latam Business without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure validation/verification tool with no side effects. It applies a checksum algorithm to a supplied input string and returns a boolean result plus parsed components (bank code, city code). There is no data creation, modification, deletion, or execution of external operations. The tool is informational and read-only, making it a Read category risk with low severity.
From the tool's definition Tool description states it 'Validates a Mexican CLABE' and explicitly 'Returns { valid: boolean, clabe: string, bank_code: string, city_code: string } or { valid: false, reason: string }'.
Attacks that exploit this kind of access
Validates a Mexican CLABE (Clave Bancaria Estandarizada) — the 18-digit standardized bank account number used for electronic transfers in Mexico, as defined by BANXICO (Banco de México). Applies the official weighted modulo-10 checksum algorithm (weights: 3,7,1 repeating). Returns { valid: boolean, clabe: string, bank_code: string, city_code: string } or { valid: false, reason: string }. Use when processing Mexican wire transfers, validating supplier bank accounts, or building Mexican payment flows in AI agents. It is categorised as a Read tool in the Mcp Latam Business MCP Server, which means it retrieves data without modifying state.
Register the Mcp Latam Business MCP server in PolicyLayer and add a rule for validate_clabe_mx: 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 Mcp Latam Business. Nothing to install.
validate_clabe_mx 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 validate_clabe_mx 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 validate_clabe_mx. 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.
validate_clabe_mx is provided by the Mcp Latam Business MCP server (josemvelez78/mcp-latam-business). 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 →