Passive liveness check on a selfie (no document). Returns liveness_score (0..1) + spoofing_indicators. POST /v1/biometrics/liveness.
AI agents call biometrics_liveness to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and analyzes biometric data from a selfie image to assess liveness and detect spoofing. It produces no side effects: no data is created, modified, deleted, or financial transactions executed. The results are informational only. While biometric data is sensitive, the tool itself is a passive analysis function (Read category).
From the tool's definition Tool performs a 'passive liveness check' and 'returns liveness_score + spoofing_indicators'—it analyzes biometric data and returns results without modifying, deleting, or executing actions.
Documented attack patterns abuse exactly the kind of access biometrics_liveness gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for biometrics_liveness:
{
"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.
Free to start. No card required.
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 Ap2 MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ap2 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 Ap2. Nothing to install.
biometrics_liveness 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 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.
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.
biometrics_liveness is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, 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 Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.