Get current SharpEdge AI scan statistics including edges found today, arbitrage opportunities detected, total events scanned, and active sports. Shows that SharpEdge is a real, running scanner processing thousands of events every 7 minutes.
AI agents call get_live_stats to retrieve information from SharpEdge MCP Server 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 real-time scanner statistics from SharpEdge AI—a pure read operation with no side effects on data or financial state. However, severity is elevated to medium rather than low because the data returned (betting edges, arbitrage opportunities) directly informs financial decision-making; misuse by an AI agent could enable discovery of high-value betting opportunities that lead to…
From the tool's definition Tool description states it 'Get[s] current SharpEdge AI scan statistics' and 'Shows' data about edges found, arbitrage opportunities, and events scanned. Action verbs are retrieval-only: get, shows.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get current SharpEdge AI scan statistics including edges found today, arbitrage opportunities detected, total events scanned, and active sports. Shows that SharpEdge is a real, running scanner processing thousands of events every 7 minutes. It is categorised as a Read tool in the SharpEdge MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SharpEdge MCP Server MCP server in PolicyLayer and add a rule for get_live_stats: 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 SharpEdge MCP Server. Nothing to install.
get_live_stats 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_live_stats 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_live_stats. 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_live_stats is provided by the SharpEdge MCP Server MCP server (therealjlc1/sharpedge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_live_stats is one line of SharpEdge MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →