Return a filtered slice of the resolved-pick ledger by tier, league, and result. Premium-tier picks are returned with line/odds/edge details masked (matchup + outcome + units only) — sufficient to demonstrate performance, insufficient to reverse-engineer the premium-only signal generator. Args: l...
Part of the Olympus Bets Analytics server.
Free to start. No card required.
AI agents call get_pick_history to retrieve information from Olympus Bets Analytics without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_pick_history only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_pick_history": {}
}
}See the full Olympus Bets Analytics policy for all 9 tools.
These attack patterns abuse exactly the kind of access get_pick_history gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Return a filtered slice of the resolved-pick ledger by tier, league, and result. Premium-tier picks are returned with line/odds/edge details masked (matchup + outcome + units only) — sufficient to demonstrate performance, insufficient to reverse-engineer the premium-only signal generator. Args: league: Optional league filter. tier: free for fully-public picks, premium for masked subscriber picks. result: WIN, LOSS, or PUSH. limit: Maximum rows (capped at 200). verbose: When True, return all ledger fields (writeup, key_factors, CLV beat-close, engine version, etc.). Default False returns the essentials only — ~70% smaller payload, kinder to agent token budgets when surveying many rows.. It is categorised as a Read tool in the Olympus Bets Analytics MCP Server, which means it retrieves data without modifying state.
Register the Olympus Bets Analytics MCP server in PolicyLayer and add a rule for get_pick_history: 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 Olympus Bets Analytics. Nothing to install.
get_pick_history 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_pick_history 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_pick_history. 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_pick_history is provided by the Olympus Bets Analytics MCP server (https://app.olympus-bets.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Olympus Bets Analytics tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.