获取 Live2D 状态：模型名称、可用表情、动作组、动画列表、参数组信息
AI agents call live2d_status to retrieve information from Live2d To Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and queries the current state of a Live2D model without making any changes, executing commands, or causing destructive operations. It is a pure read operation that returns status information about the desktop pet's current configuration and available assets.
From the tool's definition Tool name 'live2d_status' and description '获取 Live2D 状态' (Get Live2D status) indicate data retrieval. The description lists retrievable information: model name, available expressions, motion groups, animation lists, parameter groups—all read-only queries with…
Attacks that exploit this kind of access
获取 Live2D 状态：模型名称、可用表情、动作组、动画列表、参数组信息. It is categorised as a Read tool in the Live2d To Agent MCP Server, which means it retrieves data without modifying state.
Register the Live2d To Agent MCP server in PolicyLayer and add a rule for live2d_status: 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 Live2d To Agent. Nothing to install.
live2d_status 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 live2d_status 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 live2d_status. 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.
live2d_status is provided by the Live2d To Agent MCP server (lmy414/live2d-to-agent). 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 →