pm_market_authenticity
Full decomposition of a single market (by title substring or conditionId): bucket, apparent volume, taker concentration (top share plus effective traders = 1/HHI), price band, Gamma structure (book/spread/rewards), dominant flow (outcome/side/VWAP and cross-market profile), on-chain counterpartie...
This record as markdown: /tools/33unique-pm-mcp/pm-market-authenticity.md
What pm_market_authenticity does on Pm
AI agents call pm_market_authenticity 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Market title substring (for example 'Mexico England') or a conditionId (0x…). |
Parameters from the server's own tool schema.
Why pm_market_authenticity is rated Low
Even though pm_market_authenticity 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
The rule that runs pm_market_authenticity 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_market_authenticity, this is the rule to start with:
pm_market_authenticity is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Pm, apply this rule, and every pm_market_authenticity call is checked against it from then on.
Questions about pm_market_authenticity
Full decomposition of a single market (by title substring or conditionId): bucket, apparent volume, taker concentration (top share plus effective traders = 1/HHI), price band, Gamma structure (book/spread/rewards), dominant flow (outcome/side/VWAP and cross-market profile), on-chain counterparties (a FACT, not a wash label) and resolution context (✓/✗ is one sample, not skill). Only the top-N by window volume are decomposed. It is categorised as a Read tool in the Pm MCP Server, which means it retrieves data without modifying state.
pm_market_authenticity accepts 1 parameter: query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Pm MCP server in PolicyLayer and add a rule for pm_market_authenticity: 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.
pm_market_authenticity is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pm_market_authenticity 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.
Set action: deny in the PolicyLayer policy for pm_market_authenticity. 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.
pm_market_authenticity 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.
More on Pm, and thousands of servers like it.
This server
Across the catalogue