修改桌面宠物设置。可修改:window.width(200-600)、window.height(260-800)、
AI agents use settings_set to create or update resources in Live2d To Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Live2d To Agent environment.
This tool creates or modifies configuration data for a Live2D desktop pet application. The changes are reversible (window dimensions can be changed back), have no destructive or financial impact, and do not execute arbitrary code or delete data. The blast radius of misuse is minimal—an AI agent could only resize the pet window or adjust other benign settings.
From the tool's definition Tool name 'settings_set' combined with description stating it modifies (修改) desktop pet settings including window dimensions. The description shows reversible configuration changes like width and height parameters.
Attacks that exploit this kind of access
修改桌面宠物设置。可修改:window.width(200-600)、window.height(260-800)、. It is categorised as a Write tool in the Live2d To Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Live2d To Agent MCP server in PolicyLayer and add a rule for settings_set: 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.
settings_set 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 settings_set 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 settings_set. 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.
settings_set 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 →