user_agent_parse
Parse User-Agent strings: browser and version, rendering engine, OS and version, device type (mobile, tablet, desktop, TV, console, bot) with vendor/model, and bot detection that names 100+ crawlers and HTTP clients by operator and category, including AI crawlers and AI assistants (GPTBot, Claude...
This record as markdown: /tools/com-it-scorptech-x402/user-agent-parse.md
What user_agent_parse does on ScorpTech x402 API
AI agents invoke user_agent_parse to trigger actions in ScorpTech x402 API. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
ua | string | — | One User-Agent string |
uas | array | — | Several User-Agent strings (JSON array; commas inside UAs break the comma-list form) |
Parameters from the server's own tool schema.
Why user_agent_parse is rated High
user_agent_parse triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs user_agent_parse safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For user_agent_parse, this is the rule to start with:
user_agent_parse stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every user_agent_parse call is checked against it from then on.
Questions about user_agent_parse
Parse User-Agent strings: browser and version, rendering engine, OS and version, device type (mobile, tablet, desktop, TV, console, bot) with vendor/model, and bot detection that names 100+ crawlers and HTTP clients by operator and category, including AI crawlers and AI assistants (GPTBot, ClaudeBot, PerplexityBot, Bytespider, CCBot, meta-externalagent...), search, social, SEO and monitoring bots and scripted clients (curl, python-requests, headless Chrome). Up to 50 UAs per call. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/user-agent-parse. It is categorised as a Execute tool in the ScorpTech x402 API MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
user_agent_parse accepts 2 parameters: ua, uas. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for user_agent_parse: 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 ScorpTech x402 API. Nothing to install.
user_agent_parse is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the user_agent_parse 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 user_agent_parse. 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.
user_agent_parse is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
Across the catalogue