Verify the 6-digit code a returning buyer received by email (from request_buyer_code). On success returns { buyer_token, buyer_profile_id } — pass the buyer_token to get_buyer_profile to auto-fill their saved name + shipping address, and to checkout to pre-fill email and enable autonomous MPP. Fa...
Risk signalsAccepts freeform code/query input (code)
Part of the Kifly — Agentic Commerce & Payments server.
Free to start. No card required.
AI agents call verify_buyer to retrieve information from Kifly — Agentic Commerce & Payments without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though verify_buyer only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"verify_buyer": {}
}
}See the full Kifly — Agentic Commerce & Payments policy for all 18 tools.
These attack patterns abuse exactly the kind of access verify_buyer gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Verify the 6-digit code a returning buyer received by email (from request_buyer_code). On success returns { buyer_token, buyer_profile_id } — pass the buyer_token to get_buyer_profile to auto-fill their saved name + shipping address, and to checkout to pre-fill email and enable autonomous MPP. Fails with invalid_otp if the code is wrong or expired (ask them to re-check, or call request_buyer_code again). Requires the buyer:write capability.. It is categorised as a Read tool in the Kifly — Agentic Commerce & Payments MCP Server, which means it retrieves data without modifying state.
Register the Kifly — Agentic Commerce & Payments MCP server in PolicyLayer and add a rule for verify_buyer: 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 Kifly — Agentic Commerce & Payments. Nothing to install.
verify_buyer 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_buyer 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_buyer. 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_buyer is provided by the Kifly — Agentic Commerce & Payments MCP server (https://kifly.io/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Kifly — Agentic Commerce & Payments tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.