AI agents invoke compile_view_tree to trigger actions in Web Gui. 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.
While the description is empty (lowering confidence), the tool name 'compile_view_tree' and the server's focus on HTML rendering and artifact management suggest this tool executes a transformation or compilation process on view tree structures. This is more severe than a simple Read operation.
From the tool's definition Tool name 'compile_view_tree' suggests code compilation or processing of view hierarchies. Server context indicates HTML generation and artifact rendering. Compilation operations typically execute transformations on input data.
Attacks that exploit this kind of access
compile_view_tree. It is categorised as a Execute tool in the Web Gui MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Web Gui MCP server in PolicyLayer and add a rule for compile_view_tree: 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 Web Gui. Nothing to install.
compile_view_tree 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 compile_view_tree 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 compile_view_tree. 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.
compile_view_tree is provided by the Web Gui MCP server (thehzuo/gui-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 →