# pm_live_disputes

Markets that ENTERED a UMA dispute in the recent window (on-chain FACT, OO_V2 DisputePrice on Polygon), crossed with the category's HISTORICAL flip rate (also on-chain) and a 95% Wilson CI. It answers 'one of my markets is disputed — does this category usually reverse?'. It is NOT a prediction of this market's outcome. A low sample stays directional, with no headline number. Provenance is entirely on-chain.

Agent View of the PolicyLayer registry record for `pm_live_disputes`. HTML page: https://policylayer.com/tools/33unique-pm-mcp/pm-live-disputes

## Facts

- Tool: `pm_live_disputes`
- Server: Pm (`@33unique/pm-mcp`) — https://policylayer.com/tools/33unique-pm-mcp.md
- Install: `npx -y @33unique/pm-mcp`
- Homepage: https://www.npmjs.com/package/@33unique/pm-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, 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": "pm_live_disputes",
    "arguments": {}
  }
}
```

## Why pm_live_disputes is rated Low

Even though pm_live_disputes 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 pm_live_disputes to retrieve information from Pm 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 Pm:

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

## Other tools on Pm (3)

- `pm_market_authenticity` — Read — https://policylayer.com/tools/33unique-pm-mcp/pm-market-authenticity.md
- `pm_market_overview` — Read — https://policylayer.com/tools/33unique-pm-mcp/pm-market-overview.md
- `pm_resolution_risk` — Read — https://policylayer.com/tools/33unique-pm-mcp/pm-resolution-risk.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=33unique-pm-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/33unique-pm-mcp