AI agents invoke suggest_action to trigger actions in Uitars. 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 analyzes the screen and suggests (and likely triggers) click or type actions to achieve a goal. Since it drives GUI automation — performing clicks and keystrokes on the live desktop — it falls under Execute. Misuse could result in unintended GUI interactions, data submission, or launching applications.
From the tool's definition suggest_action: 'Analyze screen and suggest the next click/type action to achieve a goal' — triggers click/type actions on the GUI
Attacks that exploit this kind of access
Analyze screen and suggest the next click/type action to achieve a goal. It is categorised as a Execute tool in the Uitars MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Uitars MCP server in PolicyLayer and add a rule for suggest_action: 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 Uitars. Nothing to install.
suggest_action 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 suggest_action 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 suggest_action. 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.
suggest_action is provided by the Uitars MCP server (lxsoftroxs/uitars-mcp). 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 →