odds_check_usage
Check your API usage (requests used and remaining). Returns the latest usage values seen on a previous call; only makes a new call if no usage has been observed yet.
This record as markdown: /tools/io-github-lacausecrypto-sports-hub/odds-check-usage.md
What odds_check_usage does on Sports Hub
AI agents call odds_check_usage to retrieve information from Sports Hub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why odds_check_usage is rated Low
This tool retrieves API usage information (requests used and remaining) and performs no modifications, deletions, executions, or financial transactions. It is a pure read operation that queries usage metrics, making it a 'Read' category tool with low severity since misuse would only expose usage data with no blast radius for harmful actions.
From the tool's definition Tool name 'odds_check_usage' and description 'Check your API usage (requests used and remaining). Returns the latest usage values seen on a previous call' indicates querying/retrieving usage statistics without modification or side effects.
Attacks that exploit this kind of access
The rule that runs odds_check_usage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sports Hub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For odds_check_usage, this is the rule to start with:
odds_check_usage is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sports Hub, apply this rule, and every odds_check_usage call is checked against it from then on.
Questions about odds_check_usage
Check your API usage (requests used and remaining). Returns the latest usage values seen on a previous call; only makes a new call if no usage has been observed yet. It is categorised as a Read tool in the Sports Hub MCP Server, which means it retrieves data without modifying state.
Register the Sports Hub MCP server in PolicyLayer and add a rule for odds_check_usage: 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 Sports Hub. Nothing to install.
odds_check_usage 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 odds_check_usage 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 odds_check_usage. 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.
odds_check_usage is provided by the Sports Hub MCP server (mcp-sports-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sports Hub, and thousands of servers like it.
This server
Across the catalogue