Validate CLABE structure and checksum locally (no API call). Returns bank code, plaza, account, and check digit
AI agents call validate_clabe to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
validate_clabe performs structural and cryptographic validation of CLABE (Clave Bancaria Estandarizada) numbers, a Mexican banking standard. It retrieves and returns information (bank code, plaza, account, check digit) through local computation only, with no side effects, no data modification, and no external API calls.
From the tool's definition Tool description states 'Validate CLABE structure and checksum locally (no API call). Returns bank code, plaza, account, and check digit' — this is a pure validation function that performs local analysis and returns parsed components without modifying data,…
Documented attack patterns abuse exactly the kind of access validate_clabe gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for validate_clabe:
{
"version": "1",
"default": "deny",
"tools": {
"validate_clabe": {}
}
}validate_clabe 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.
Validate CLABE structure and checksum locally (no API call). Returns bank code, plaza, account, and check digit. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for validate_clabe: 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 Ap2. Nothing to install.
validate_clabe 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 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. 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 is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, 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.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.