Low Risk

validate_phone

Check whether a phone number is enrolled in Nequi

How to control validate_phone ↓

What validate_phone does on Mcp Afip

AI agents call validate_phone to retrieve information from Mcp Afip without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why validate_phone needs a policy

This is a read operation that queries whether a phone number exists in the Nequi system. It has no side effects, does not modify data, does not execute arbitrary code, and does not involve financial transactions. The low severity reflects minimal risk even if misused, as phone number validation carries limited blast radius compared to other categories.

From the tool's definition The tool 'validate_phone' with description 'Check whether a phone number is enrolled in Nequi' performs a lookup/verification query. It retrieves enrollment status information without modifying, executing operations, or causing financial transactions.

Documented attack patterns abuse exactly the kind of access validate_phone gives an agent:

How to control validate_phone

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Afip, and nothing reaches the server without passing your rules. This is the rule we recommend for validate_phone:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "validate_phone": {}
  }
}

validate_phone is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Afip — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about validate_phone

What does the validate_phone tool do? +

Check whether a phone number is enrolled in Nequi. It is categorised as a Read tool in the Mcp Afip MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on validate_phone? +

Register the Mcp Afip MCP server in PolicyLayer and add a rule for validate_phone: 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 Afip. Nothing to install.

What risk level is validate_phone? +

validate_phone is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit validate_phone? +

Yes. Add a rate_limit block to the validate_phone 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.

How do I block validate_phone completely? +

Set action: deny in the PolicyLayer policy for validate_phone. 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.

What MCP server provides validate_phone? +

validate_phone is provided by the Mcp Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Afip tool call.

Start from Mcp Afip, 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.

1300 Mcp Afip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.