Send a 6-digit verification code to a returning buyer's email so they can prove the account is theirs and recover their saved name + shipping address on this connection — without pasting any token. Call this when the buyer says they've shopped with Kifly before and gives you their email; then ask...
Part of the Kifly — Agentic Commerce & Payments server.
Free to start. No card required.
AI agents use request_buyer_code to create or modify resources in Kifly — Agentic Commerce & Payments. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call request_buyer_code repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Kifly — Agentic Commerce & Payments.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"request_buyer_code": {
"limits": [
{
"counter": "request_buyer_code_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Kifly — Agentic Commerce & Payments policy for all 18 tools.
These attack patterns abuse exactly the kind of access request_buyer_code gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Send a 6-digit verification code to a returning buyer's email so they can prove the account is theirs and recover their saved name + shipping address on this connection — without pasting any token. Call this when the buyer says they've shopped with Kifly before and gives you their email; then ask them to read you the code from their inbox and call verify_buyer. Returns { sent: true }. If the email has no account yet, fails with buyer_not_found — in that case call register_buyer instead. Requires the buyer:write capability (marketplace/network keys).. It is categorised as a Write tool in the Kifly — Agentic Commerce & Payments MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kifly — Agentic Commerce & Payments MCP server in PolicyLayer and add a rule for request_buyer_code: 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.
request_buyer_code 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 request_buyer_code 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 request_buyer_code. 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.
request_buyer_code is provided by the Kifly — Agentic Commerce & Payments MCP server (https://kifly.ai/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.