IDPay: biometric 1:1 comparison between a live selfie and a document photo. Returns a similarity score (0-1) and a boolean match verdict at Unico
AI agents call face_match 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.
The tool performs identity verification by comparing biometric data and returning a similarity score and match verdict. This is a read-only operation that retrieves/queries matching results without creating, modifying, deleting data, or committing financial obligations. While sensitive data is involved (biometric comparison), the tool itself only reads and compares, making it a Read category risk.
From the tool's definition Tool description specifies 'biometric 1:1 comparison' and 'returns a similarity score and a boolean match verdict' — this is a comparison operation with no side effects, data modification, or financial transaction.
Documented attack patterns abuse exactly the kind of access face_match 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 face_match:
{
"version": "1",
"default": "deny",
"tools": {
"face_match": {}
}
} face_match 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.
IDPay: biometric 1:1 comparison between a live selfie and a document photo. Returns a similarity score (0-1) and a boolean match verdict at Unico. 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 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 Ap2. Nothing to install.
face_match 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 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.
Set action: deny in the PolicyLayer policy for 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.
face_match 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.