Validates the format of a Colombian Cédula de Ciudadanía (CC) — the national identity document for Colombian citizens. Verifies that the number is between 6 and 10 digits as required by the Registraduría Nacional. Returns { valid: boolean, cc: string } or { valid: false, reason: string }. Use whe...
AI agents call validate_cc_co 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 tool retrieves and validates format information about an identity document number without querying databases, modifying records, executing code, deleting data, or making financial transactions. It is a pure validation/query operation with read-only semantics.
From the tool's definition Tool description states it 'Verifies that the number is between 6 and 10 digits' and 'Returns { valid: boolean, cc: string }' — it performs validation checks only.
Attacks that exploit this kind of access
Validates the format of a Colombian Cédula de Ciudadanía (CC) — the national identity document for Colombian citizens. Verifies that the number is between 6 and 10 digits as required by the Registraduría Nacional. Returns { valid: boolean, cc: string } or { valid: false, reason: string }. Use when processing Colombian individual tax filings, employment contracts, or KYC onboarding flows requiring a verified Colombian citizen ID. Note: checksum validation is not publicly available for CC numbers. 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_cc_co: 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_cc_co 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_cc_co 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_cc_co. 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_cc_co 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 →