Retrieve a seller's public profile: name, location (city/region/country), storefront URL, delivery fee, delivery coverage, and catalog size. Call this before create_cart or set_shipping_address to validate that the seller ships to the buyer's area or to set expectations about catalog size. delive...
Part of the Kifly — Agentic Commerce & Payments server.
Free to start. No card required.
AI agents call get_seller 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_seller 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_seller": {}
}
}See the full Kifly — Agentic Commerce & Payments policy for all 18 tools.
These attack patterns abuse exactly the kind of access get_seller 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 seller's public profile: name, location (city/region/country), storefront URL, delivery fee, delivery coverage, and catalog size. Call this before create_cart or set_shipping_address to validate that the seller ships to the buyer's area or to set expectations about catalog size. delivery_coverage is { states, cities } — the US state codes (e.g. 'CA', 'NE') and city names the seller delivers to; an address is eligible when its region matches a covered state OR its city matches a covered city. delivery_fee_cents is the flat fee added at checkout; catalog_size is the total number of products listed. delivery_zones (legacy postal-code list) is still returned for backward compatibility but new agents should read delivery_coverage. For network (cross-seller) tokens, pass handle to name which seller you're asking about (e.g. handle: 'bay-clothing-district'). Handle lookup is case-insensitive — 'BayClothingDistrict' and 'bayclothingdistrict' both resolve. Seller-scoped tokens may omit handle — their own seller is implicit.. 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_seller: 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_seller 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_seller 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_seller. 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_seller 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.