List all UI states defined in a project.
AI agents call list_states to retrieve information from Qontinui Web MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists existing UI state configurations from a project. It performs a read-only query with no ability to modify, delete, or execute operations. The blast radius is minimal—exposure would only allow an attacker to enumerate UI states already stored in the system, which is informational but not immediately exploitable for data modification or unauthorized actions.
From the tool's definition Tool name 'list_states' and description 'List all UI states defined in a project' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List all UI states defined in a project. It is categorised as a Read tool in the Qontinui Web MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qontinui Web MCP Server MCP server in PolicyLayer and add a rule for list_states: 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 Qontinui Web MCP Server. Nothing to install.
list_states 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_states 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_states. 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_states is provided by the Qontinui Web MCP Server MCP server (qontinui/qontinui-web-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 →