Create an Onfido applicant — the person record that documents, live photos, and checks attach to. Required before any verification.
AI agents use create_applicant 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 tool creates a new record (person/applicant) in what appears to be an identity verification or KYC (Know Your Customer) system. This is a Write operation as it creates data reversibly. The severity is high because creating applicant records can be used to establish false identities, commit fraud, or perform unauthorized identity verification workflows that may have downstream financial or legal consequences.
From the tool's definition Tool description states 'Create an Onfido applicant' and 'Required before any verification,' indicating it creates a new person record in an identity verification system.
Documented attack patterns abuse exactly the kind of access create_applicant 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 create_applicant:
{
"version": "1",
"default": "deny",
"tools": {
"create_applicant": {
"limits": [
{
"counter": "create_applicant_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_applicant 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.
Create an Onfido applicant — the person record that documents, live photos, and checks attach to. Required before any verification. 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 create_applicant: 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.
create_applicant 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 create_applicant 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 create_applicant. 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.
create_applicant 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.