Team overview: roster + record + upcoming schedule. Accepts team name or ID.
AI agents call team_overview to retrieve information from Nba Stats without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates existing team data (roster, record, schedule) without creating, modifying, deleting, or executing any operations. It is a pure data query with no state changes or external effects. Low severity because misuse would only return information the user could obtain through other public channels, with no ability to harm systems or data.
From the tool's definition Tool description states 'Team overview: roster + record + upcoming schedule' — retrieves team roster information, win-loss record, and schedule data. The verb 'accepts' indicates a query operation with no side effects.
Documented attack patterns abuse exactly the kind of access team_overview gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nba Stats, and nothing reaches the server without passing your rules. This is the rule we recommend for team_overview:
{
"version": "1",
"default": "deny",
"tools": {
"team_overview": {}
}
}team_overview is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Team overview: roster + record + upcoming schedule. Accepts team name or ID. It is categorised as a Read tool in the Nba Stats MCP Server, which means it retrieves data without modifying state.
Register the Nba Stats MCP server in PolicyLayer and add a rule for team_overview: 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 Nba Stats. Nothing to install.
team_overview 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 team_overview 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 team_overview. 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.
team_overview is provided by the Nba Stats MCP server (labeveryday/nba-stats-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nba Stats, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Nba Stats tools catalogued and risk-classified — across an index of 43,000+ MCP servers.