Get the KYC status of a buyer the partner has previously sent through Transak. Look up by partnerCustomerId (preferred — your stable id) or email. Returns kycStatus (NOT_SUBMITTED, IN_REVIEW, APPROVED, REJECTED, EXPIRED), tier, country, and the timestamps. Use this to skip re-KYC for returning bu...
AI agents call get_kyc_status 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 retrieves and returns existing KYC (Know Your Customer) status data without modifying, creating, or deleting any records. The description explicitly states it 'gets' and 'returns' information, with no mention of updates, mutations, or side effects. While KYC data is sensitive, the tool itself performs only a lookup query.
From the tool's definition Tool name 'get_kyc_status' and description 'Get the KYC status... Returns kycStatus, tier, country, and the timestamps' indicate a read-only query operation that retrieves previously stored KYC status information.
Documented attack patterns abuse exactly the kind of access get_kyc_status 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 get_kyc_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_kyc_status": {}
}
}get_kyc_status 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.
Get the KYC status of a buyer the partner has previously sent through Transak. Look up by partnerCustomerId (preferred — your stable id) or email. Returns kycStatus (NOT_SUBMITTED, IN_REVIEW, APPROVED, REJECTED, EXPIRED), tier, country, and the timestamps. Use this to skip re-KYC for returning buyers and unlock higher limits. 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 get_kyc_status: 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.
get_kyc_status 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 get_kyc_status 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 get_kyc_status. 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.
get_kyc_status 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.