선수의 시즌별 + 통산 기록(라커룸). ⚠️ 이 선수가 뛴 모든 리그·팀 합산 전체 커리어
AI agents call player_career to retrieve information from Kaist Beast Baseball without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns historical player statistics with no side effects. It performs a simple read operation that retrieves or displays existing data without creating, modifying, deleting, or executing any operations. No reversible modifications, irreversible deletions, code execution, or financial transactions are involved.
From the tool's definition The tool description indicates it retrieves historical career statistics ('시즌별 + 통산 기록' = season-by-season and career totals records), presenting a player's complete career data across all leagues and teams.
Attacks that exploit this kind of access
선수의 시즌별 + 통산 기록(라커룸). ⚠️ 이 선수가 뛴 모든 리그·팀 합산 전체 커리어. It is categorised as a Read tool in the Kaist Beast Baseball MCP Server, which means it retrieves data without modifying state.
Register the Kaist Beast Baseball MCP server in PolicyLayer and add a rule for player_career: 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 Kaist Beast Baseball. Nothing to install.
player_career 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 player_career 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 player_career. 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.
player_career is provided by the Kaist Beast Baseball MCP server (mw-jeong/kaist-beast-baseball-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 →