팀 투수 운용/부하 — 등판수·선발수·누적이닝·볼넷·탈삼진·최근등판. 로테이션·피로 판단.
AI agents call pitcher_usage 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 analyzes baseball league data to provide pitcher usage information for team analysis purposes. It retrieves statistical data from the gameone.kr data source without creating, modifying, deleting, or executing any operations with side effects. The tool supports the read-only analysis workflow described in the server's purpose.
From the tool's definition Tool description indicates it retrieves and reports pitcher statistics and usage metrics (등장수/등판수·선발수·누적이닝·볼넷·탈삼진·최근등장) for rotation and fatigue analysis. No modification, deletion, or execution of external operations is mentioned.
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 pitcher_usage: 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.
pitcher_usage 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 pitcher_usage 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 pitcher_usage. 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.
pitcher_usage 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 →