x402_check

Check if a URL requires x402 payment. Returns payment details if 402 status is returned.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/x402-check.md

WHAT IT DOES

What x402_check does on CoWork OS

AI agents call x402_check to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why x402_check is rated Low

The tool performs a read/query operation by checking a URL's HTTP status to determine if payment is required. It only retrieves payment details (if a 402 response is returned) and does not initiate or commit any financial transaction. No side effects are implied.

From the tool's definition 'Check if a URL requires x402 payment. Returns payment details if 402 status is returned.'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs x402_check safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For x402_check, this is the rule to start with:

x402_check Allowed

x402_check is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "x402_check": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every x402_check call is checked against it from then on.

FAQ

Questions about x402_check

What does the x402_check tool do? +

Check if a URL requires x402 payment. Returns payment details if 402 status is returned. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on x402_check? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for x402_check: 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 CoWork OS. Nothing to install.

What risk level is x402_check? +

x402_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit x402_check? +

Yes. Add a rate_limit block to the x402_check 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.

How do I block x402_check completely? +

Set action: deny in the PolicyLayer policy for x402_check. 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.

What MCP server provides x402_check? +

x402_check is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →