Validates a postal code format for a given Latin American country using the official pattern for that country. Returns { valid: boolean, postal_code: string, country: string, format: string }. Supports BR (8-digit CEP), MX (5-digit CP), CL (7-digit with dash), AR (4-digit legacy or CPA alphanumer...
AI agents call validate_postal_code_latam 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.
validate_postal_code_latam performs format validation and pattern matching against official postal code schemas across LatAm countries. It retrieves no data, modifies nothing, and cannot trigger external actions or financial transactions. The response is a simple boolean validation result. This is a pure read operation with minimal blast radius — misuse would only yield false positives/negatives in form validation.
From the tool's definition Tool validates postal code format and returns { valid: boolean, postal_code: string, country: string, format: string }.
Attacks that exploit this kind of access
Validates a postal code format for a given Latin American country using the official pattern for that country. Returns { valid: boolean, postal_code: string, country: string, format: string }. Supports BR (8-digit CEP), MX (5-digit CP), CL (7-digit with dash), AR (4-digit legacy or CPA alphanumeric), CO (6-digit). Use in e-commerce checkout validation, address verification, or logistics workflows across LatAm markets. 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_postal_code_latam: 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_postal_code_latam 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_postal_code_latam 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_postal_code_latam. 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_postal_code_latam 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 →