identify_x402_client
agentscan: Identify an x402 client by User-Agent: monitor, indexer, grader or HTTP library, with call rate. For any other User-Agent use parse_user_agent; for a whole access log use analyze_agent_traffic. Returns whether a User-Agent is a known x402 monitor, indexer, grader, SDK, AI fetcher, bot ...
This record as markdown: /tools/dev-tanod-tanod/identify-x402-client.md
What identify_x402_client does on Tanod
AI agents call identify_x402_client to retrieve information from Tanod without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
ua | object | — | Optional: a User-Agent string to identify (at most 512 characters; not stored or echoed). Empty or absent: the whole table. |
Parameters from the server's own tool schema.
Why identify_x402_client is rated Low
Even though identify_x402_client only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs identify_x402_client safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For identify_x402_client, this is the rule to start with:
identify_x402_client is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every identify_x402_client call is checked against it from then on.
Questions about identify_x402_client
agentscan: Identify an x402 client by User-Agent: monitor, indexer, grader or HTTP library, with call rate. For any other User-Agent use parse_user_agent; for a whole access log use analyze_agent_traffic. Returns whether a User-Agent is a known x402 monitor, indexer, grader, SDK, AI fetcher, bot or HTTP library, what it does and its observed call rate at one seller (requests a day, per route, unpaid share); no ua: the full table. Input: optional ua; GET takes it as a query parameter. Reviewed table from one seller's logs and public docs; observed kinds are not confirmed by the operators. Unknown is known false (charged). The ua is not stored. Typically under 0.1 s. Price: USD 0.001. Free: 10 agent-index calls per IP per UTC day. Docs: https://tanod.dev/learn/x402-client-identify-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
identify_x402_client accepts 1 parameter: ua. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for identify_x402_client: 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 Tanod. Nothing to install.
identify_x402_client 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 identify_x402_client 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 identify_x402_client. 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.
identify_x402_client is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue