xml_xpath
Run XPath 1.0 queries over XML you supply (RSS/Atom, SOAP, sitemaps, SVG, config) or over HTML for scraping: returns matched elements/attributes/text with their paths, text, attributes and outer markup, or the number/string/boolean result of an expression. Namespaces are auto-registered (default ...
This record as markdown: /tools/com-it-scorptech-x402/xml-xpath.md
What xml_xpath does on ScorpTech x402 API
AI agents invoke xml_xpath 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 |
|---|---|---|---|
xml | string | — | XML document |
html | string | — | HTML document (lenient parser), alternative to xml |
limit | integer | — | |
xpath | string | — | XPath 1.0 expression |
xpaths | object | — | Several named expressions {"name": "xpath"} (max 20) |
outerXml | boolean | — | Include each element's markup (truncated to 2000 chars) |
namespaces | object | — | Extra prefix -> namespace URI bindings |
Parameters from the server's own tool schema.
Why xml_xpath is rated High
xml_xpath 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.
Risk signalsAccepts raw HTML/template content (html)
Attacks that exploit this kind of access
The rule that runs xml_xpath 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 xml_xpath, this is the rule to start with:
xml_xpath 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 xml_xpath call is checked against it from then on.
Questions about xml_xpath
Run XPath 1.0 queries over XML you supply (RSS/Atom, SOAP, sitemaps, SVG, config) or over HTML for scraping: returns matched elements/attributes/text with their paths, text, attributes and outer markup, or the number/string/boolean result of an expression. Namespaces are auto-registered (default namespace as prefix d). Safe parser: no network, no external entities, DTD entities rejected. POST JSON body {xml or html, xpath}. Price: $0.003 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/xml-xpath. 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.
xml_xpath accepts 7 parameters: xml, html, limit, xpath, xpaths, outerXml, namespaces. 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 xml_xpath: 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.
xml_xpath 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 xml_xpath 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 xml_xpath. 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.
xml_xpath 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