Retrieve a repeat buyer's saved name, email, and default shipping address. At the start of every purchase flow, ask the buyer in plain language: 'Are you a returning Kifly shopper? What's the email on your Kifly account?' — never ask them to paste a token. If they have a Kifly account, recover it...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Kifly — Agentic Commerce & Payments server.
Free to start. No card required.
AI agents call get_buyer_profile 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 get_buyer_profile 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": {
"get_buyer_profile": {}
}
}See the full Kifly — Agentic Commerce & Payments policy for all 18 tools.
These attack patterns abuse exactly the kind of access get_buyer_profile 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.
Retrieve a repeat buyer's saved name, email, and default shipping address. At the start of every purchase flow, ask the buyer in plain language: 'Are you a returning Kifly shopper? What's the email on your Kifly account?' — never ask them to paste a token. If they have a Kifly account, recover it by email: call request_buyer_code with their email, ask them for the 6-digit code we email them, then call verify_buyer to obtain their buyer_token, and finally call this tool with that token to auto-fill name, email, and shipping — they skip all manual data entry. (Alternative if email verification isn't available: send them the one-click sign-in link https://kifly.ai/buyer?return_url=<encoded_current_chat_url> — they sign in with Google and return with their details; the same link creates an account if they're new.) Use the returned name and default_shipping_address to auto-fill set_shipping_address. Pass the buyer_token to checkout so Stripe pre-fills their email. Returns { name, email, default_shipping_address } where default_shipping_address may be null if the buyer hasn't saved one yet — if null, collect the address normally then call save_buyer_address so it's pre-filled next time.. 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 get_buyer_profile: 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.
get_buyer_profile 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_buyer_profile 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_buyer_profile. 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_buyer_profile 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.