Passive liveness on a selfie (no comparison image). Returns liveness_score + spoofing signals. POST /v1/biometrics/liveness.
AI agents call liveness_check 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.
The tool performs biometric liveness detection on a selfie image and returns analysis results (liveness_score and spoofing signals). This is fundamentally a read operation—it retrieves and analyzes data without side effects. No data is modified, deleted, or used to trigger financial/operational changes.
From the tool's definition Tool description states 'Passive liveness on a selfie (no comparison image). Returns liveness_score + spoofing signals.' This is a passive analysis endpoint that reads/analyzes biometric data without modifying, executing code, destroying data, or processing…
Documented attack patterns abuse exactly the kind of access liveness_check gives an agent:
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 liveness_check:
{
"version": "1",
"default": "deny",
"tools": {
"liveness_check": {}
}
} liveness_check is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Passive liveness on a selfie (no comparison image). Returns liveness_score + spoofing signals. 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.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for liveness_check: 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.
liveness_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the liveness_check 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 liveness_check. 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.
liveness_check 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.
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.