Agent Governance: ALLOW/FRICTION/REVIEW/BLOCK Decision Patterns
How do you control what an AI agent can do in your store? The KYAI Policy Engine uses four decision levels — ALLOW, FRICTION, REVIEW, BLOCK — to enforce trust-based governance on every agent action.
Executive summary
How do you control what an AI agent can do in your store? The KYAI Policy Engine uses four decision levels — ALLOW, FRICTION, REVIEW, BLOCK — to enforce trust-based governance on every agent action.
Published
2026-03-20
11 min
Author
Platform Strategy Team
Commerce strategy analysts
The platform strategy team translates AI, commerce, and protocol shifts into actionable guidance for operational teams.
View profileCategory
Agentic Commerce
AI agents can search your catalog, compare prices, build carts, and initiate payments. But should they be able to do all of that without any oversight? The answer depends on the action, the amount, the agent's trust history, and the merchant's risk tolerance. Agent governance is the framework that makes these decisions systematic rather than ad-hoc. Without it, every agent interaction is either fully open — creating risk — or fully blocked — losing revenue. The KYAI Policy Engine solves this by introducing four decision levels that apply to every agent action.
Why governance matters for agentic commerce
In traditional e-commerce, governance is implicit. A human buyer navigates your store, and the store's UX guides and constrains their behavior. Checkout limits, quantity caps, and fraud detection work because a human is in the loop. With AI agents, that implicit governance disappears. An agent can execute hundreds of actions per minute, process complex multi-step flows, and interact with your systems in ways your checkout flow was never designed to handle. Without explicit governance rules, merchants face two bad options: block agents entirely and miss the opportunity, or allow everything and accept uncontrolled risk.
The four decision levels
The KYAI Policy Engine evaluates every agent action against a chain of rules and assigns one of four decision levels. Each level represents a different balance between speed and safety.
- 1**ALLOW**: The action proceeds immediately with no friction. Used for low-risk operations like searching the catalog, viewing product details, or checking availability. The agent experiences zero latency overhead.
- 2**FRICTION**: The action proceeds but with an additional verification step. Used for medium-risk operations like adding items to a cart or applying a discount code. The agent must provide additional context or the user sees a confirmation prompt.
- 3**REVIEW**: The action is queued for human review before execution. Used for high-value or unusual operations like placing an order above a threshold, requesting a bulk purchase, or using a new payment method. A merchant operator must approve before the action completes.
- 4**BLOCK**: The action is denied outright. Used for prohibited operations like attempting to purchase restricted items, exceeding hard spending limits, or when the agent's trust score falls below the minimum threshold. The agent receives a clear rejection with the reason.
The KYAI rule chain
KYAI evaluates rules in a defined order, and the most restrictive matching rule wins. The rule chain includes five standard rules that every merchant starts with: amount limit check (blocks transactions above the merchant's configured maximum), velocity check (adds friction when an agent exceeds a threshold of actions per time window), trust score check (requires review for agents below a minimum trust level), category restriction (blocks purchases of prohibited product categories), and protocol validation (ensures the payment protocol meets the merchant's requirements). Merchants can customize thresholds, add custom rules, and override defaults for specific agents or agent classes.
Configuring merchant rules
Every merchant has different risk tolerance and operational capacity. A small boutique might set a low REVIEW threshold at $100 and BLOCK at $500. A large marketplace might ALLOW up to $1,000 and only REVIEW above $5,000. The configuration is declarative — merchants define rules in their dashboard or via API, and KYAI applies them consistently to every agent interaction. The key principle is that merchants own their governance policy. The platform provides the engine, the defaults, and the tooling, but the merchant decides what is allowed, what needs friction, what requires review, and what is blocked.
The trust score connection
Trust scores and governance are deeply connected. An agent's trust score is a dynamic value that reflects its history: how many successful transactions it has completed, whether it has triggered chargebacks or disputes, how consistently it provides accurate user information, and whether it follows stated policies. Higher trust scores can unlock more permissive governance rules. A brand-new agent might face FRICTION on a $50 purchase, while a well-established agent with a high trust score might get ALLOW on a $500 purchase from the same merchant. This creates a natural incentive for agents to behave reliably.
Real-world governance scenarios
- 1**Scenario 1 — Low-risk browse**: Agent searches catalog, views 15 products, checks availability on 3. All actions are ALLOW. Total latency overhead: zero.
- 2**Scenario 2 — Medium purchase**: Agent builds a cart of $150. FRICTION is triggered: the user receives a confirmation prompt showing the cart summary before checkout proceeds.
- 3**Scenario 3 — High-value order**: Agent attempts a $2,500 purchase. REVIEW is triggered: the order is queued and a merchant operator receives a notification to approve or reject.
- 4**Scenario 4 — Suspicious pattern**: Agent attempts 50 add-to-cart operations in 30 seconds. Velocity check triggers BLOCK. The agent receives a clear message explaining the rate limit.
- 5**Scenario 5 — Restricted product**: Agent attempts to purchase an age-restricted product without verified age data. Category restriction triggers BLOCK with a specific reason code.
Good governance does not slow down agents. It slows down risky actions and accelerates safe ones. The goal is to make trust a competitive advantage, not a bottleneck.
Frequently asked questions
What is KYAI?
KYAI (Know Your AI) is the policy engine that governs agent actions in the AgenticMCPStores platform. It evaluates every agent action against a chain of merchant-defined rules and assigns one of four decision levels: ALLOW, FRICTION, REVIEW, or BLOCK. It is protocol-agnostic, meaning the same rules apply whether the agent uses ACP, AP2, or x402.
Can merchants override the default governance rules?
Yes. Merchants have full control over their governance policy. They can adjust thresholds for each decision level, add custom rules, create exceptions for specific agents or agent classes, and even disable default rules if their risk model differs from the platform defaults.
Does governance slow down agents?
ALLOW actions have zero latency overhead. FRICTION adds a brief verification step. Only REVIEW adds meaningful delay because it requires human approval. The goal of the governance framework is to make low-risk actions fast and only introduce delay where the risk justifies it. Well-configured governance actually improves agent throughput by providing clear rules upfront.
How is agent governance different from rate limiting?
Rate limiting is a blunt instrument that caps the number of requests regardless of context. Agent governance is context-aware: it considers the action type, the amount, the agent's trust score, the merchant's configuration, and the protocol being used. A trusted agent making a legitimate high-value purchase is treated differently from an unknown agent making rapid small requests. Governance is about trust-based decisions, not just throughput caps.
Sources and references
- Model Context Protocol
Anthropic
- OWASP API Security Top 10
OWASP
- Schema.org Product
Schema.org
Related articles
Agentic Commerce
Zero-Click Commerce: When the Agent Buys Without the User Visiting Your Store
The majority of AI-assisted purchases in 2026 will never produce a click on your website. The agent compares, decides and executes. Your store doesn't need to be visited — it needs to be understood.
Agentic Commerce
ACP vs AP2 vs x402: Complete Guide to Agentic Payment Protocols
Three protocols are shaping how AI agents handle payments. ACP (Stripe/OpenAI) for fiat, AP2 (Google) for cart mandates, and x402 (Coinbase/Cloudflare) for USDC stablecoins. Here's when to use each.
Agentic Commerce
Agentic Auto-Discovery: Why 90% of Platforms Are Invisible to AI Agents
We ran a simple test: we sent an AI agent to discover the top 10 agentic commerce platforms. 9 of 10 returned 404 on llms.txt. 10 of 10 had no agent-policy.json. Only one was autonomously discoverable.