Low Risk

get_todays_projections

Return today's free sports betting projections published by Olympus Bets Analytics. Each projection includes the matchup, market (spread/moneyline/total), the line, the American odds at publication, the calibrated model probability, the edge versus the market, the Kelly-sized units, the confidenc...

Part of the Olympus Bets Analytics server.

get_todays_projections is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE OLYMPUS BETS ANALYTICS →

Free to start. No card required.

AI agents call get_todays_projections 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_todays_projections 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_todays_projections": {}
  }
}

See the full Olympus Bets Analytics policy for all 9 tools.

Get this rule live on your own Olympus Bets Analytics server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY OLYMPUS BETS ANALYTICS →

View all 9 tools →

These attack patterns abuse exactly the kind of access get_todays_projections gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_todays_projections only ever does what you allow.

SECURE OLYMPUS BETS ANALYTICS →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_todays_projections tool do? +

Return today's free sports betting projections published by Olympus Bets Analytics. Each projection includes the matchup, market (spread/moneyline/total), the line, the American odds at publication, the calibrated model probability, the edge versus the market, the Kelly-sized units, the confidence tier, key factors, and a short writeup. These are PUBLIC projections — the same set published on https://app.olympus-bets.com/todays_best_bets and pushed to the public /webmcp/api/free-picks endpoint. Premium tier projections are not exposed here. Args: league: Optional league filter (e.g. "NBA", "NHL", "MLB", "CBB", "NFL", "SOCCER", "LOL", "GOLF"). Omit to return all leagues. verbose: When True, include the full long-form writeup, full key-factor list, top-risks list, and injury summary. Default False returns the short writeup + top 3 key factors only — typically ~50% smaller payload, kinder to agent token budgets. Set verbose=True when an agent specifically wants the detail (e.g., user asked "explain this pick"). Returns: {date, total, leagues_active, projections: [...]}. It is categorised as a Read tool in the Olympus Bets Analytics MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_todays_projections? +

Register the Olympus Bets Analytics MCP server in PolicyLayer and add a rule for get_todays_projections: 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.

What risk level is get_todays_projections? +

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

Can I rate-limit get_todays_projections? +

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

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

get_todays_projections 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.

Enforce policy on every Olympus Bets Analytics tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.