# polymarket_health_check

Check server readiness and basic connectivity.

Agent View of the PolicyLayer registry record for `polymarket_health_check`. HTML page: https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-health-check

## Facts

- Tool: `polymarket_health_check`
- Server: Polymarket MCP Server (`asthetech/mewcp-polymarket`) — https://policylayer.com/tools/asthetech-cl-mcp-polymarket.md
- Homepage: https://github.com/AStheTECH/mewcp-polymarket
- Risk category: Read (Low risk)
- Registry record: grade D, 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": "polymarket_health_check",
    "arguments": {}
  }
}
```

## Why polymarket_health_check is rated Low

A health check is a non-invasive read operation that verifies server status without retrieving sensitive market data, modifying state, or triggering transactions. It has minimal blast radius if misused by an agent.

From the tool's own definition: "Tool name 'polymarket_health_check' and description 'Check server readiness and basic connectivity' indicate a diagnostic query with no data modification or side effects."

## Use case

AI agents call polymarket_health_check to retrieve information from Polymarket MCP Server 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 Polymarket MCP Server:

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

## Other tools on Polymarket MCP Server (10)

- `polymarket_cancel_order` — Destructive — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-cancel-order.md
- `polymarket_create_order` — Financial — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-create-order.md
- `polymarket_get_events` — Read — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-get-events.md
- `polymarket_get_market` — Read — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-get-market.md
- `polymarket_get_markets` — Read — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-get-markets.md
- `polymarket_get_midpoint` — Read — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-get-midpoint.md
- `polymarket_get_orderbook` — Read — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-get-orderbook.md
- `polymarket_get_orders` — Read — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-get-orders.md
- `polymarket_get_user_positions` — Read — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-get-user-positions.md
- `polymarket_get_user_trades` — Read — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-get-user-trades.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=asthetech-cl-mcp-polymarket · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/asthetech-cl-mcp-polymarket