pandascore_get_incidents
Get recent changes and incidents (new matches, score updates, roster changes). Useful for tracking updates since a given timestamp.
This record as markdown: /tools/io-github-lacausecrypto-sports-hub/pandascore-get-incidents.md
What pandascore_get_incidents does on Sports Hub
AI agents call pandascore_get_incidents 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 pandascore_get_incidents is rated Low
This tool retrieves historical incident and change data from a sports API. It has no side effects, cannot modify data, execute code, delete records, or move money. It is a straightforward read operation for querying sports event updates.
From the tool's definition Tool description states 'Get recent changes and incidents' and 'tracking updates since a given timestamp' — purely retrieval of data with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs pandascore_get_incidents 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 pandascore_get_incidents, this is the rule to start with:
pandascore_get_incidents 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 pandascore_get_incidents call is checked against it from then on.
Questions about pandascore_get_incidents
Get recent changes and incidents (new matches, score updates, roster changes). Useful for tracking updates since a given timestamp. 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 pandascore_get_incidents: 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.
pandascore_get_incidents 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 pandascore_get_incidents 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 pandascore_get_incidents. 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.
pandascore_get_incidents 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