screening_listas
Screening de un nombre o entidad contra listas de sanciones internacionales (OFAC, UE, UK, Canada), personas expuestas politicamente (PEP de los paises con servicio: MX, BR, CO, AR, DO, CA, US) y listas nacionales (Mexico, Brasil, Colombia, Argentina, R. Dominicana). Envia 'name'; opcional 'count...
This record as markdown: /tools/com-resetparatodos-verifica/screening-listas.md
What screening_listas does on RESET Verifica
AI agents call screening_listas as a supporting operation in RESET Verifica workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | |
tax_id | string | — | |
country | string | — | |
certificate | boolean | — |
Parameters from the server's own tool schema.
Why screening_listas is rated Low
Without any rule in front of it, every call an agent makes to screening_listas happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.
Attacks that exploit this kind of access
The rule that runs screening_listas safely
PolicyLayer is an MCP gateway: it sits between your AI agents and RESET Verifica, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For screening_listas, this is the rule to start with:
screening_listas gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect RESET Verifica, apply this rule, and every screening_listas call is checked against it from then on.
Questions about screening_listas
Screening de un nombre o entidad contra listas de sanciones internacionales (OFAC, UE, UK, Canada), personas expuestas politicamente (PEP de los paises con servicio: MX, BR, CO, AR, DO, CA, US) y listas nacionales (Mexico, Brasil, Colombia, Argentina, R. Dominicana). Envia 'name'; opcional 'country' (ISO, p.ej. MX) y 'tax_id' para el cruce nacional; 'certificate'=true para recibir una constancia PDF (base64). Devuelve coincidencias con puntaje 0-100 y un registro por cada lista consultada (limpia o con hits). Cuesta SCREEN. Es evidencia, no una certificacion de cumplimiento: un resultado 'sin coincidencias' no exime del deber de debida diligencia. It is categorised as a Other tool in the RESET Verifica MCP Server, which means it performs auxiliary operations.
screening_listas accepts 4 parameters: name, tax_id, country, certificate. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the RESET Verifica MCP server in PolicyLayer and add a rule for screening_listas: 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 RESET Verifica. Nothing to install.
screening_listas is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the screening_listas 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 screening_listas. 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.
screening_listas is provided by the RESET Verifica MCP server (https://mcp.resetparatodos.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on RESET Verifica, and thousands of servers like it.
This server
Across the catalogue