pm_live_disputes

SERVERPm SOURCE@33unique/pm-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/33unique-pm-mcp/pm-live-disputes.md

WHAT IT DOES

What pm_live_disputes does on Pm

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.

RISK

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pm_live_disputes safely

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

pm_live_disputes Allowed

pm_live_disputes 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": {
    "pm_live_disputes": {}
  }
}

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

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

FAQ

Questions about pm_live_disputes

What does the pm_live_disputes tool do? +

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. It is categorised as a Read tool in the Pm MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pm_live_disputes? +

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

What risk level is pm_live_disputes? +

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

Can I rate-limit pm_live_disputes? +

Yes. Add a rate_limit block to the pm_live_disputes 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 pm_live_disputes completely? +

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

pm_live_disputes is provided by the Pm MCP server (@33unique/pm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pm, and thousands of servers like it.

This server

All 4 Pm tools →

Across the catalogue

The MCP Attack Database →

Guides

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