AI agents call stackchan_home as a supporting operation in Stackchan workflows.
The description is completely empty, so the tool's behavior cannot be determined from the description alone. Based on the name 'stackchan_home' and the context of sibling tools (movement, expressions, speech for a robot), this likely returns the robot to a home/default position, which would be an Execute or Write action. However, without a description, confidence is very low.
From the tool's definition Tool name is 'stackchan_home' and description is empty or uninformative.
Documented attack patterns abuse exactly the kind of access stackchan_home 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_home:
{
"version": "1",
"default": "deny",
"tools": {
"stackchan_home": {
"limits": [
{
"counter": "stackchan_home_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}stackchan_home gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
stackchan_home. It is categorised as a Other tool in the Stackchan MCP Server, which means it performs auxiliary operations.
Register the Stackchan MCP server in PolicyLayer and add a rule for stackchan_home: 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_home is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the stackchan_home 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_home. 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_home 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.