加载 Live2D 模型。指定包含 .model3.json 的目录路径,
AI agents invoke model_load to trigger actions in Live2d To Agent. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Loading a model from a filesystem path triggers an external operation with side effects (loading files into memory, changing the active model state). It is not a simple read, but it also doesn't destructively delete data. The ability to specify an arbitrary directory path could be misused to load unintended files, raising the severity to medium.
From the tool's definition 加载 Live2D 模型。指定包含 .model3.json 的目录路径 — triggers an external operation to load a model from a specified directory path
Attacks that exploit this kind of access
加载 Live2D 模型。指定包含 .model3.json 的目录路径,. It is categorised as a Execute tool in the Live2d To Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Live2d To Agent MCP server in PolicyLayer and add a rule for model_load: 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.
model_load is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the model_load 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 model_load. 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.
model_load 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 →