Run an Australian identity check over a SET of identity documents. A vision model reads each document (which ID it is, which fields it shows — name/photo/address/signature — and its issue date); a deterministic engine then tallies them against a scheme and reports whether identity is established,...
AI agents call verify_identity to retrieve information from OpenWarrant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
scheme | string | — | |
documents | array | Yes |
Parameters from the server's own tool schema.
This is a Read operation—it retrieves and queries data from identity documents to assess compliance against a verification scheme, returning a report. However, severity is elevated to 'medium' rather than 'low' because the tool processes sensitive personal information (names, photos, addresses, signatures) and its output directly determines access/onboarding decisions.
From the tool's definition Tool description states it "reads each document" via vision model, "reports whether identity is established", and returns what is "missing if not." No modification, deletion, or execution of code is described.
Attacks that exploit this kind of access
Run an Australian identity check over a SET of identity documents. A vision model reads each document (which ID it is, which fields it shows — name/photo/address/signature — and its issue date); a deterministic engine then tallies them against a scheme and reports whether identity is established, and exactly what's still missing if not. USE THIS WHEN someone needs to verify a person's identity from their documents — KYC / onboarding / "do these documents satisfy the 100-point check?" Pass ALL the person's documents together (a passport alone is 70 points; the check needs >= 100). documents is a list, each item ONE of: {"url": "https://..."} (public link, fetched server-side) or {"bytes_b64": "...", "filename": "passport.pdf"} (inline). Up to 10. scheme: "afp_100_point" (points, default) or "austrac_safe_harbour" (category combinations). Returns {established, points/target or satisfied_path, documents[] (per-document: type, fields shown, whether it counted and why-not), reason, accepts, ...}. This is identity COVERAGE, not a forgery judgment — run verify_document for authenticity. Documents are never stored. It is categorised as a Read tool in the OpenWarrant MCP Server, which means it retrieves data without modifying state.
verify_identity accepts 2 parameters: scheme, documents. Required: documents. The full parameter table on this page comes from the server's own tool schema.
Register the OpenWarrant MCP server in PolicyLayer and add a rule for verify_identity: 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 OpenWarrant. Nothing to install.
verify_identity 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 verify_identity 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 verify_identity. 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.
verify_identity is provided by the OpenWarrant MCP server (https://www.stipple.sh/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →