AI agents call find_ui_elements to retrieve information from Kwin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
find_ui_elements retrieves or queries UI element data from the KWin session—a read operation with no side effects. The empty description lowers confidence slightly, but the name and context among other automation tools clearly indicate a query function. No data is created, modified, deleted, or code executed by this tool alone.
From the tool's definition Tool name 'find_ui_elements' indicates a search/query operation for UI components. The sibling tools (accessibility_tree, clipboard_get, focus_window, keyboard_*) suggest this server enables GUI automation, and find_ui_elements appears to be the…
Documented attack patterns abuse exactly the kind of access find_ui_elements gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kwin, and nothing reaches the server without passing your rules. This is the rule we recommend for find_ui_elements:
{
"version": "1",
"default": "deny",
"tools": {
"find_ui_elements": {}
}
}find_ui_elements is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
find_ui_elements. It is categorised as a Read tool in the Kwin MCP Server, which means it retrieves data without modifying state.
Register the Kwin MCP server in PolicyLayer and add a rule for find_ui_elements: 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 Kwin. Nothing to install.
find_ui_elements 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 find_ui_elements 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 find_ui_elements. 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.
find_ui_elements is provided by the Kwin MCP server (isac322/kwin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kwin, 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.
30 Kwin tools catalogued and risk-classified — across an index of 43,000+ MCP servers.