[보정 도구] 소표본 empirical Bayes shrinkage — '1타석 OPS 2.0' 같은 허수를
AI agents call regressed_batting 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 performs statistical regression analysis on batting metrics to provide corrected estimates. It retrieves and transforms existing data without creating, modifying, deleting, or executing external operations. The shrinkage method is a read-only analytical operation. Severity is low because misuse would only produce incorrect analysis, not cause data loss or harmful external effects.
From the tool's definition Tool name 'regressed_batting' and description indicate statistical calculation/analysis ('empirical Bayes shrinkage') applied to baseball batting data.
Attacks that exploit this kind of access
[보정 도구] 소표본 empirical Bayes shrinkage — '1타석 OPS 2.0' 같은 허수를. 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 regressed_batting: 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.
regressed_batting 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 regressed_batting 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 regressed_batting. 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.
regressed_batting 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 →