AI agents invoke full_pipeline to trigger actions in Live2D Automation MCP Server. 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.
The tool name 'full_pipeline' strongly suggests it orchestrates the entire Live2D model generation process end-to-end, encompassing multiple operations including analysis, segmentation, rigging, physics configuration, mesh creation, and export. This constitutes an Execute classification as it triggers a complex chain of external operations.
From the tool's definition Tool name 'full_pipeline' on a server described as providing 'a full pipeline for creating layered art meshes and motion files through a suite of specialized animation tools'
Documented attack patterns abuse exactly the kind of access full_pipeline gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Live2D Automation MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for full_pipeline:
{
"version": "1",
"default": "deny",
"tools": {
"full_pipeline": {
"limits": [
{
"counter": "full_pipeline_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}full_pipeline stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
full_pipeline. It is categorised as a Execute tool in the Live2D Automation MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Live2D Automation MCP Server MCP server in PolicyLayer and add a rule for full_pipeline: 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 Automation MCP Server. Nothing to install.
full_pipeline 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 full_pipeline 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 full_pipeline. 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.
full_pipeline is provided by the Live2D Automation MCP Server MCP server (j621111/live2d-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Live2D Automation MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Live2D Automation MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.