Gera variações matematicamente válidas de um CPF possivelmente errado.
AI agents invoke generate_valid_variations to trigger actions in Cpf Validador. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool generates mathematically valid CPF variations from a potentially incorrect CPF. While it sounds like a computation, it produces valid CPF numbers that can be used for identity fraud or enumeration attacks against Brazilian taxpayer IDs.
From the tool's definition Gera variações matematicamente válidas de um CPF possivelmente errado
Documented attack patterns abuse exactly the kind of access generate_valid_variations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cpf Validador, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_valid_variations:
{
"version": "1",
"default": "deny",
"tools": {
"generate_valid_variations": {
"limits": [
{
"counter": "generate_valid_variations_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}generate_valid_variations stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Gera variações matematicamente válidas de um CPF possivelmente errado. It is categorised as a Execute tool in the Cpf Validador MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cpf Validador MCP server in PolicyLayer and add a rule for generate_valid_variations: 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 Cpf Validador. Nothing to install.
generate_valid_variations is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the generate_valid_variations 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 generate_valid_variations. 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.
generate_valid_variations is provided by the Cpf Validador MCP server (opastorello/cpf-validador). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cpf Validador, 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.
6 Cpf Validador tools catalogued and risk-classified — across an index of 43,000+ MCP servers.