AI agents call list_design_systems to retrieve information from Web Gui without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool lists design systems, which is a read-only data retrieval operation with no side effects. Even without explicit description, the 'list_' prefix universally indicates enumeration/retrieval. There is no data modification, deletion, code execution, or financial impact. Confidence is slightly reduced due to empty description, but the naming convention is unambiguous.
From the tool's definition Tool name 'list_design_systems' indicates a query/retrieval operation. No description provided, but based on naming pattern and sibling tools like 'get_design_system_summary' and 'list_artifacts', this is clearly a listing/retrieval function.
Attacks that exploit this kind of access
list_design_systems. It is categorised as a Read tool in the Web Gui MCP Server, which means it retrieves data without modifying state.
Register the Web Gui MCP server in PolicyLayer and add a rule for list_design_systems: 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.
list_design_systems 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 list_design_systems 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 list_design_systems. 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.
list_design_systems 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 →