AI agents invoke stackchan_move to trigger actions in Stackchan. 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 and server context strongly suggest this tool triggers physical movement of the Stack-chan robot. This is an Execute-category action as it triggers an external physical operation. The description is empty, which lowers confidence. Severity is medium because physical robot movement could cause unintended consequences in the real world, but the robot appears small/consumer-grade.
From the tool's definition Tool name 'stackchan_move' on a server that 'enables speech, listening, vision, movement, and facial expressions through MCP tool calls' — 'movement' is the relevant capability.
Documented attack patterns abuse exactly the kind of access stackchan_move gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Stackchan, and nothing reaches the server without passing your rules. This is the rule we recommend for stackchan_move:
{
"version": "1",
"default": "deny",
"tools": {
"stackchan_move": {
"limits": [
{
"counter": "stackchan_move_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stackchan_move 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.
stackchan_move. It is categorised as a Execute tool in the Stackchan MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Stackchan MCP server in PolicyLayer and add a rule for stackchan_move: 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 Stackchan. Nothing to install.
stackchan_move 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 stackchan_move 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 stackchan_move. 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.
stackchan_move is provided by the Stackchan MCP server (migratorywhale/stackchan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Stackchan, 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.
12 Stackchan tools catalogued and risk-classified — across an index of 43,000+ MCP servers.