apifootball_get_status
Get your API-Football account status including subscription plan, request usage, and limits.
This record as markdown: /tools/io-github-lacausecrypto-sports-hub/apifootball-get-status.md
What apifootball_get_status does on Sports Hub
AI agents call apifootball_get_status 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 apifootball_get_status is rated Low
This tool queries account metadata without side effects. It is a straightforward retrieval operation (Read category). Severity is low because the information exposed (subscription tier, usage stats) is non-sensitive account administrative data that does not enable unauthorized access, code execution, or financial transactions. The tool does not permit destructive or write operations.
From the tool's definition Tool name 'get_status' and description explicitly state it retrieves account information: 'subscription plan, request usage, and limits.' No modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
The rule that runs apifootball_get_status 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 apifootball_get_status, this is the rule to start with:
apifootball_get_status 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 apifootball_get_status call is checked against it from then on.
Questions about apifootball_get_status
Get your API-Football account status including subscription plan, request usage, and limits. 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 apifootball_get_status: 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.
apifootball_get_status 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 apifootball_get_status 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 apifootball_get_status. 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.
apifootball_get_status 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