Upload a live photo (selfie) for an applicant, used by facial_similarity_photo reports. Sent as multipart/form-data. NOTE: Onfido recommends capturing live photos via their SDK; direct API upload may be restricted on some accounts.
AI agents use upload_live_photo to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.
This is a Write operation because it creates/stores new data (a live photo) reversibly without deleting or modifying existing records. While the context involves payment authorization and identity verification (AP2 protocol), the tool itself performs data creation, not financial transactions.
From the tool's definition Tool 'upload_live_photo' creates and stores a new artifact (a live photo/selfie) in the system for an applicant, sent as multipart/form-data.
Documented attack patterns abuse exactly the kind of access upload_live_photo 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 upload_live_photo:
{
"version": "1",
"default": "deny",
"tools": {
"upload_live_photo": {
"limits": [
{
"counter": "upload_live_photo_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}upload_live_photo stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Upload a live photo (selfie) for an applicant, used by facial_similarity_photo reports. Sent as multipart/form-data. NOTE: Onfido recommends capturing live photos via their SDK; direct API upload may be restricted on some accounts. It is categorised as a Write tool in the Mcp Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for upload_live_photo: 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.
upload_live_photo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the upload_live_photo 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 upload_live_photo. 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.
upload_live_photo 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.