Finds the best paid services for a task. Describe what you need; returns the top 3 pay-per-call services ranked by real 30-day usage (calls, unique payers), price fit and metadata quality, with price, network and why_recommended for each. Live data from the agent-economy service index. The trust ...
AI agents call navi_service_scout to retrieve information from Navi X402 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
task | string | Yes | Natural-language description of what you need, e.g. 'translate text to japanese' or 'get crypto price history' |
category | string | — | Optional category filter: inference | data | search | media | social | trading | infra |
max_price | number | — | Optional maximum price per call in USDC, e.g. 0.01 |
Parameters from the server's own tool schema.
navi_service_scout is fundamentally a search/lookup tool that queries a service index and returns ranked results. While the server enables financial transactions via USDC payments, this particular tool does not move money itself—it only provides informational data to help agents decide which services to pay for. The actual payment mechanism is handled separately by the server infrastructure ('settled automatically').
From the tool's definition Tool 'returns the top 3 pay-per-call services ranked by real 30-day usage (calls, unique payers), price fit and metadata quality, with price, network and why_recommended for each.' It retrieves and queries data from a service index with no side effects on…
Attacks that exploit this kind of access
Finds the best paid services for a task. Describe what you need; returns the top 3 pay-per-call services ranked by real 30-day usage (calls, unique payers), price fit and metadata quality, with price, network and why_recommended for each. Live data from the agent-economy service index. The trust layer for agents deciding which service to pay. (Paid via x402: $0.005 USDC per call on Base, settled automatically.). It is categorised as a Read tool in the Navi X402 MCP Server, which means it retrieves data without modifying state.
navi_service_scout accepts 3 parameters: task, category, max_price. Required: task. The full parameter table on this page comes from the server's own tool schema.
Register the Navi X402 MCP server in PolicyLayer and add a rule for navi_service_scout: 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 Navi X402. Nothing to install.
navi_service_scout 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 navi_service_scout 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 navi_service_scout. 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.
navi_service_scout is provided by the Navi X402 MCP server (navi-x402-mcp). 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 →