Trigger the KYC verification check for a customer. Sandbox auto-progresses business customers through the hosted KYC flow once documents are uploaded. Idempotent — returns 422
AI agents call verify_customer 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 initiates a KYC (Know Your Customer) verification process but does not directly write, modify, delete, or move funds. It reads/validates customer data against verification requirements and returns status (including error 422).
From the tool's definition Trigger the KYC verification check for a customer. Sandbox auto-progresses business customers through the hosted KYC flow once documents are uploaded. Idempotent — returns 422
Documented attack patterns abuse exactly the kind of access verify_customer 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 verify_customer:
{
"version": "1",
"default": "deny",
"tools": {
"verify_customer": {}
}
} verify_customer 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.
Trigger the KYC verification check for a customer. Sandbox auto-progresses business customers through the hosted KYC flow once documents are uploaded. Idempotent — returns 422. 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 verify_customer: 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.
verify_customer 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_customer 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_customer. 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_customer 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.