짜낸 라인업(타순·수비·투수 운용 등)을 저장해 다음에 다시 볼 수 있게 한다.
AI agents use save_lineup to create or update resources in Kaist Beast Baseball — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kaist Beast Baseball environment.
This tool creates and stores user-generated lineup data (batting order, defensive assignments, pitcher rotations). It is a Write operation because it persistently stores configuration data that can be retrieved and presumably updated later.
From the tool's definition Tool description: '짜낸 라인업(타순·수비·투수 운용 등)을 저장해 다음에 다시 볼 수 있게 한다' translates to 'saves the arranged lineup (batting order, defense, pitcher management, etc.) so it can be viewed again next time.' The verb 'save' and the intent to persist created lineup…
Attacks that exploit this kind of access
짜낸 라인업(타순·수비·투수 운용 등)을 저장해 다음에 다시 볼 수 있게 한다. It is categorised as a Write tool in the Kaist Beast Baseball MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kaist Beast Baseball MCP server in PolicyLayer and add a rule for save_lineup: 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.
save_lineup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_lineup 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 save_lineup. 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.
save_lineup 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 →