Low Risk

reverse_lookup_player

Retrieve a table of player information given a list of player ids :param player_ids: list of player ids :type player_ids: list :param key_type: name of the key type being looked up (one of "mlbam", "retro", "bbref", or "fangraphs") :type key_type: str :rtype: :class:...

Part of the MLB Stats Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call reverse_lookup_player to retrieve information from MLB Stats Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though reverse_lookup_player only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

etweisberg-mlb-mcp.yaml
tools:
  reverse_lookup_player:
    rules:
      - action: allow

See the full MLB Stats Server policy for all 46 tools.

Tool Name reverse_lookup_player
Category Read
Risk Level Low

View all 46 tools →

Agents calling read-class tools like reverse_lookup_player have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the reverse_lookup_player tool do? +

Retrieve a table of player information given a list of player ids :param player_ids: list of player ids :type player_ids: list :param key_type: name of the key type being looked up (one of "mlbam", "retro", "bbref", or "fangraphs") :type key_type: str :rtype: :class:`pandas.core.frame.DataFrame` . It is categorised as a Read tool in the MLB Stats Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on reverse_lookup_player? +

Add a rule in your Intercept YAML policy under the tools section for reverse_lookup_player. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the MLB Stats Server MCP server.

What risk level is reverse_lookup_player? +

reverse_lookup_player is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit reverse_lookup_player? +

Yes. Add a rate_limit block to the reverse_lookup_player rule in your Intercept 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.

How do I block reverse_lookup_player completely? +

Set action: deny in the Intercept policy for reverse_lookup_player. 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.

What MCP server provides reverse_lookup_player? +

reverse_lookup_player is provided by the MLB Stats Server MCP server (etweisberg/mlb-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on MLB Stats Server

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.