probe_402_support
Make one GET (or HEAD) request to a public URL and report whether it answers with an HTTP 402 payment challenge, which scheme, and the decoded terms. Redirects are reported, not followed. Private and local addresses are refused. Never pays anything.
This record as markdown: /tools/402mcp/probe-402-support.md
What probe_402_support does on 402mcp
AI agents call probe_402_support to retrieve information from 402mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why probe_402_support is rated Low
Even though probe_402_support 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 probe_402_support safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 402mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For probe_402_support, this is the rule to start with:
probe_402_support 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 402mcp, apply this rule, and every probe_402_support call is checked against it from then on.
Questions about probe_402_support
Make one GET (or HEAD) request to a public URL and report whether it answers with an HTTP 402 payment challenge, which scheme, and the decoded terms. Redirects are reported, not followed. Private and local addresses are refused. Never pays anything. It is categorised as a Read tool in the 402mcp MCP Server, which means it retrieves data without modifying state.
Register the 402 MCP server in PolicyLayer and add a rule for probe_402_support: 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 402mcp. Nothing to install.
probe_402_support 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 probe_402_support 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 probe_402_support. 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.
probe_402_support is provided by the 402 MCP server (402MCP/402mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 402, and thousands of servers like it.
This server
Across the catalogue