AI agents call mlb_team_result to retrieve information from Baseball without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical game results or team performance data from the MLB Stats API. It has no side effects, does not modify data, and simply queries existing information.
From the tool's definition Tool name 'mlb_team_result' combined with server description stating it provides 'game schedules, results, team information, and player lookups' indicates data retrieval.
Documented attack patterns abuse exactly the kind of access mlb_team_result gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Baseball, and nothing reaches the server without passing your rules. This is the rule we recommend for mlb_team_result:
{
"version": "1",
"default": "deny",
"tools": {
"mlb_team_result": {}
}
}mlb_team_result 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.
mlb_team_result. It is categorised as a Read tool in the Baseball MCP Server, which means it retrieves data without modifying state.
Register the Baseball MCP server in PolicyLayer and add a rule for mlb_team_result: 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 Baseball. Nothing to install.
mlb_team_result 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 mlb_team_result 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 mlb_team_result. 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.
mlb_team_result is provided by the Baseball MCP server (mpizza/mcp_mlb_statsapi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Baseball, 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.
3 Baseball tools catalogued and risk-classified — across an index of 43,000+ MCP servers.