Get merchant navigation flow for a domain or platform key (e.g. '_platform_etsy'). Returns pre_steps (how to navigate checkout) and platform notes. Call BEFORE starting checkout to understand the multi-step flow.
AI agents call get_merchant_hints to retrieve information from Z Zero without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | The main domain of the checkout page, e.g. 'amazon.com' or 'shopify.com'. Strip 'www.' prefix. |
Parameters from the server's own tool schema.
This tool retrieves informational data about checkout flows for different platforms. It performs a lookup/query operation that returns guidance data without modifying state, executing operations, or committing financial transactions. The most severe related action on the server (execute_payment, request_payment_token) are separate tools. This tool itself is purely informational and read-only.
From the tool's definition Tool description states it 'Returns pre_steps (how to navigate checkout) and platform notes' and is called 'BEFORE starting checkout' — it retrieves and queries merchant navigation information with no side effects.
Attacks that exploit this kind of access
Get merchant navigation flow for a domain or platform key (e.g. '_platform_etsy'). Returns pre_steps (how to navigate checkout) and platform notes. Call BEFORE starting checkout to understand the multi-step flow. It is categorised as a Read tool in the Z Zero MCP Server, which means it retrieves data without modifying state.
get_merchant_hints accepts 1 parameter: domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the Z Zero MCP server in PolicyLayer and add a rule for get_merchant_hints: 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 Z Zero. Nothing to install.
get_merchant_hints 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_merchant_hints 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_merchant_hints. 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_merchant_hints is provided by the Z Zero MCP server (z-zero-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →