verificacion_completa
Transaccion completa (COMBO): empresa por RFC + factura (XML CFDI) + pago (XML CEP) en una sola operacion, a precio combinado. Cuesta COMBO.
This record as markdown: /tools/com-resetparatodos-verifica/verificacion-completa.md
What verificacion_completa does on RESET Verifica
AI agents call verificacion_completa as a supporting operation in RESET Verifica workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
rfc | string | Yes | |
refs | string | — | |
cep_xml | string | Yes | |
cfdi_xml | string | Yes |
Parameters from the server's own tool schema.
Why verificacion_completa is rated Low
Without any rule in front of it, every call an agent makes to verificacion_completa 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 verificacion_completa 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 verificacion_completa, this is the rule to start with:
verificacion_completa 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 verificacion_completa call is checked against it from then on.
Questions about verificacion_completa
Transaccion completa (COMBO): empresa por RFC + factura (XML CFDI) + pago (XML CEP) en una sola operacion, a precio combinado. Cuesta COMBO. It is categorised as a Other tool in the RESET Verifica MCP Server, which means it performs auxiliary operations.
verificacion_completa accepts 4 parameters: rfc, refs, cep_xml, cfdi_xml. Required: rfc, cep_xml, cfdi_xml. 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 verificacion_completa: 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.
verificacion_completa 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 verificacion_completa 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 verificacion_completa. 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.
verificacion_completa 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