Low Risk

biometrics_face_match

Compare a selfie against a document photo (RG / CNH front). Returns match_score (0..1) and liveness verdict. POST /v1/biometrics/face-match.

How to control biometrics_face_match ↓

What biometrics_face_match does on Mcp Afip

AI agents call biometrics_face_match 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 biometrics_face_match needs a policy

This tool performs biometric verification by comparing facial images and returning match scores. While it accesses sensitive personal biometric data (selfies, government ID photos), it does not create, modify, delete, or execute actions with side effects.

From the tool's definition Tool description states it 'Compare[s] a selfie against a document photo' and 'Returns match_score (0..1) and liveness verdict' — purely retrieval and comparison of biometric data without modification or deletion.

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

How to control biometrics_face_match

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 biometrics_face_match:

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

biometrics_face_match 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 biometrics_face_match

What does the biometrics_face_match tool do? +

Compare a selfie against a document photo (RG / CNH front). Returns match_score (0..1) and liveness verdict. POST /v1/biometrics/face-match. 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 biometrics_face_match? +

Register the Mcp Afip MCP server in PolicyLayer and add a rule for biometrics_face_match: 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 biometrics_face_match? +

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

Can I rate-limit biometrics_face_match? +

Yes. Add a rate_limit block to the biometrics_face_match 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 biometrics_face_match completely? +

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

biometrics_face_match 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.