# 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.

Agent View of the PolicyLayer registry record for `probe_402_support`. HTML page: https://policylayer.com/tools/402mcp/probe-402-support

## Facts

- Tool: `probe_402_support`
- Server: 402mcp (`402MCP/402mcp`) — https://policylayer.com/tools/402mcp.md
- Homepage: https://github.com/402MCP/402mcp
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "probe_402_support",
    "arguments": {}
  }
}
```

## 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.

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 402mcp:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "probe_402_support": {}
  }
}
```

## Other tools on 402mcp (6)

- `decode_402_challenge` — Read — https://policylayer.com/tools/402mcp/decode-402-challenge.md
- `get_best_payment_solution` — Read — https://policylayer.com/tools/402mcp/get-best-payment-solution.md
- `get_scheme_reference` — Read — https://policylayer.com/tools/402mcp/get-scheme-reference.md
- `get_solution` — Read — https://policylayer.com/tools/402mcp/get-solution.md
- `recommend_payment_rail` — Read — https://policylayer.com/tools/402mcp/recommend-payment-rail.md
- `search_402_solutions` — Read — https://policylayer.com/tools/402mcp/search-402-solutions.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=402mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/402mcp
