Low Risk

get_sharp_line

Answer an odds question about a fixture in ONE call (natural language in, worked line out). Resolves the fixture, picks the consensus line, the best price per outcome across books, and de-vigged fair odds from the sharpest book — returning a ready-to-read summary plus the full comparison. Prefer ...

Risk signalsAccepts freeform code/query input (query)

Part of the Infersports server.

get_sharp_line 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 INFERSPORTS →

Free to start. No card required.

AI agents call get_sharp_line to retrieve information from Infersports 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_sharp_line 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_sharp_line": {}
  }
}

See the full Infersports policy for all 14 tools.

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

ENFORCE ON MY INFERSPORTS →

View all 14 tools →

These attack patterns abuse exactly the kind of access get_sharp_line 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_sharp_line only ever does what you allow.

SECURE INFERSPORTS →

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

What does the get_sharp_line tool do? +

Answer an odds question about a fixture in ONE call (natural language in, worked line out). Resolves the fixture, picks the consensus line, the best price per outcome across books, and de-vigged fair odds from the sharpest book — returning a ready-to-read summary plus the full comparison. Prefer this over chaining find_match → compare_lines. Args: query: natural-language fixture, e.g. "Arsenal vs Man City" or a single team. market_type: "1x2", "asian_handicap" (default) or "totals". period: "full_time" (default) or "half_time". format: odds format — decimal | hk | malay | american | indonesian | probability. sport: optional filter — "football" or "basketball". date: optional UTC date "YYYY-MM-DD" to disambiguate same-name fixtures. verbosity: "full" (default) or "terse". "terse" empties the per-book books array inside comparison to save tokens; the summary and worked numbers are kept either way. On an ambiguous query, status is "ambiguous" and ask_user carries a disambiguation prompt — do not assume a match; ask the user or re-call with a more specific query. A decision block (safe_to_proceed / ask_user / next_action) pre-computes the go/no-go — branch on it instead of re-judging the result.. It is categorised as a Read tool in the Infersports MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_sharp_line? +

Register the Infersports MCP server in PolicyLayer and add a rule for get_sharp_line: 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 Infersports. Nothing to install.

What risk level is get_sharp_line? +

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

Can I rate-limit get_sharp_line? +

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

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

get_sharp_line is provided by the Infersports MCP server (https://api.infersports.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Infersports tool call.

Deterministic rules across all 14 Infersports 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.