Get the top traders on Predict.fun by volume, P&L, or trade count
AI agents call get_leaderboard 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 is a read-only query operation that retrieves and displays leaderboard statistics. It has no side effects, does not execute code or external operations, and does not modify, create, or destroy any data. The blast radius of misuse is minimal—an agent could only consume leaderboard data to inform decisions, with no impact on the platform itself.
From the tool's definition Tool name 'get_leaderboard' and description 'Get the top traders on Predict.fun by volume, P&L, or trade count' indicates retrieval of aggregated ranking data with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
Get the top traders on Predict.fun by volume, P&L, or trade count. 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_leaderboard: 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_leaderboard 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_leaderboard 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_leaderboard. 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_leaderboard 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 →