AI agents invoke autogui_stop_task to trigger actions in MCPHub. 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.
This tool stops an active GUI automation task, which is an execute operation that controls external automation workflows. While not immediately destructive, stopping a running task can interrupt critical processes and cause data loss or inconsistent state if the task was mid-operation. Confidence is high because the Chinese description clearly indicates active task termination.
From the tool's definition '停止当前正在运行的GUI自动化任务' (Stop the currently running GUI automation task). The tool terminates an external automation process, which is an Execute action that triggers effects on system state.
Attacks that exploit this kind of access
停止当前正在运行的GUI自动化任务。. It is categorised as a Execute tool in the MCPHub MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCPHub MCP server in PolicyLayer and add a rule for autogui_stop_task: 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 MCPHub. Nothing to install.
autogui_stop_task 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 autogui_stop_task 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 autogui_stop_task. 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.
autogui_stop_task is provided by the MCPHub MCP server (jayden-dong/mcphub). 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 →