Get recently resolved markets with their outcomes and payout info
AI agents call get_resolved_markets to retrieve information from Predictfun without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries resolved market data without creating, modifying, deleting, or executing any operations. It is purely informational—reading outcome and payout details from the prediction market protocol. There is no capability to alter market states, execute trades, transfer funds, or trigger external actions. The blast radius of misuse is minimal, limited to potential information disclosure.
From the tool's definition Tool name 'get_resolved_markets' and description 'Get recently resolved markets with their outcomes and payout info' indicate a read-only retrieval operation.
Attacks that exploit this kind of access
Get recently resolved markets with their outcomes and payout info. It is categorised as a Read tool in the Predictfun MCP Server, which means it retrieves data without modifying state.
Register the Predictfun MCP server in PolicyLayer and add a rule for get_resolved_markets: 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 Predictfun. Nothing to install.
get_resolved_markets 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 get_resolved_markets 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 get_resolved_markets. 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.
get_resolved_markets is provided by the Predictfun MCP server (paulieb14/predictfun-subgraphs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →