util_x402_server_probe
Probe an x402 server end-to-end: discovery, status, tools, reliability, and OpenAPI.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/util-x402-server-probe.md
What util_x402_server_probe does on Delx MCP Server
AI agents call util_x402_server_probe to retrieve information from Delx MCP Server 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 |
|---|---|---|---|
url | string | Yes | x402 server origin |
timeout | integer | — | Timeout in seconds (1-15) |
Parameters from the server's own tool schema.
Why util_x402_server_probe is rated Low
The tool performs read-only reconnaissance of an x402 server — it discovers endpoints, checks status, lists tools, and retrieves OpenAPI specs. All operations are passive information gathering with no data modification or side effects. Severity is low since it only reads/queries remote server metadata, though probing external servers could leak information about internal infrastructure.
From the tool's definition Probe an x402 server end-to-end: discovery, status, tools, reliability, and OpenAPI
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs util_x402_server_probe safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_x402_server_probe, this is the rule to start with:
util_x402_server_probe 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 Delx MCP Server, apply this rule, and every util_x402_server_probe call is checked against it from then on.
Questions about util_x402_server_probe
Probe an x402 server end-to-end: discovery, status, tools, reliability, and OpenAPI. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
util_x402_server_probe accepts 2 parameters: url, timeout. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for util_x402_server_probe: 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 Delx MCP Server. Nothing to install.
util_x402_server_probe 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 util_x402_server_probe 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 util_x402_server_probe. 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.
util_x402_server_probe is provided by the Delx MCP Server MCP server (delx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue