Low Risk

biometrics_liveness

Passive liveness check on a selfie (no document). Returns liveness_score (0..1) + spoofing_indicators. POST /v1/biometrics/liveness.

How to control biometrics_liveness ↓

What biometrics_liveness does on Mcp Afip

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

This tool analyzes biometric data from a selfie and returns a confidence score and spoofing indicators. While it processes sensitive personal biometric information, the operation is non-destructive, read-only (returns analysis results only), and produces no side effects on server state, financial systems, or user accounts.

From the tool's definition POST /v1/biometrics/liveness returns liveness_score (0..1) + spoofing_indicators — performs analysis on a selfie without modifying any data, creating financial obligations, or triggering side effects.

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

How to control biometrics_liveness

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

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

biometrics_liveness 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_liveness

What does the biometrics_liveness tool do? +

Passive liveness check on a selfie (no document). Returns liveness_score (0..1) + spoofing_indicators. POST /v1/biometrics/liveness. 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_liveness? +

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

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

Can I rate-limit biometrics_liveness? +

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

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

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