Get current MLB injury report.
AI agents call get_injuries to retrieve information from MLB SportRadar 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 real-time injury report information from the SportRadar API. It performs a read-only query with no side effects, no code execution, no data modification, and no financial impact. The blast radius of misuse is minimal—an AI agent could retrieve injury data repeatedly or with unusual queries, but cannot cause harm beyond information access or resource exhaustion.
From the tool's definition Tool name 'get_injuries' and description 'Get current MLB injury report' indicate a retrieval operation that queries and returns existing injury data without modifying, executing code, or altering any state.
Attacks that exploit this kind of access
Get current MLB injury report. It is categorised as a Read tool in the MLB SportRadar MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MLB SportRadar MCP Server MCP server in PolicyLayer and add a rule for get_injuries: 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 MLB SportRadar MCP Server. Nothing to install.
get_injuries 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_injuries 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_injuries. 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_injuries is provided by the MLB SportRadar MCP Server MCP server (robcerda/mlb-sportradar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →