AI agents call autogui_get_history to retrieve information from MCPHub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves execution history of GUI automation tasks, which is a read-only operation with no side effects. It queries past data rather than executing new operations, modifying data, or deleting anything. Even though it relates to automation infrastructure, the specific function is data retrieval, placing it firmly in the Read category.
From the tool's definition Tool name 'autogui_get_history' and description '获取当前GUI自动化任务的执行历史' (Get the execution history of the current GUI automation task) indicate retrieval of historical data without modification.
Attacks that exploit this kind of access
获取当前GUI自动化任务的执行历史。. It is categorised as a Read tool in the MCPHub MCP Server, which means it retrieves data without modifying state.
Register the MCPHub MCP server in PolicyLayer and add a rule for autogui_get_history: 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_get_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the autogui_get_history 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_get_history. 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_get_history 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 →