Production-grade web page intelligence for AI agents. Single canonical analysis block, structured repository sub-object for github/gitlab pages (stars/forks/language/topics), link taxonomy (internal | external | social_media | navigation | asset), links_summary aggregator, contextual next actions...
AI agents call navi_page_context 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 |
|---|---|---|---|
url | string | Yes | The URL of the web page to analyze (article, repo, product page, etc.) |
Parameters from the server's own tool schema.
The tool retrieves and analyzes web page content, returning structured intelligence about page properties, links, and signals. While the server processes USDC payments, the tool itself only reads and queries data without creating, modifying, deleting, or executing arbitrary code. The financial transaction is a separate infrastructure concern (per-request billing), not an action performed by this tool.
From the tool's definition Tool performs 'web page intelligence' analysis and retrieval of structured data: 'canonical analysis block', 'repository sub-object', 'link taxonomy', 'links_summary', 'boolean signals'.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
Production-grade web page intelligence for AI agents. Single canonical analysis block, structured repository sub-object for github/gitlab pages (stars/forks/language/topics), link taxonomy (internal | external | social_media | navigation | asset), links_summary aggregator, contextual next actions, 16+ boolean signals. Clean v2 response shape. (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_page_context accepts 1 parameter: url. Required: url. 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_page_context: 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_page_context 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_page_context 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_page_context. 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_page_context 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 →