List existing E2E test scenarios saved in Assert. Use this to audit coverage before generating new tests. Supports pagination. Project filtering is reserved but not currently enforced by the API.
AI agents call assert_list to retrieve information from Assert without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves metadata about existing test scenarios without executing them, modifying them, or triggering any side effects. It is a pure read operation used for inspection and auditing purposes. The low severity reflects minimal blast radius — listing test scenarios poses negligible security risk.
From the tool's definition Tool description explicitly states 'List existing E2E test scenarios' and 'audit coverage' — retrieval operations with no modification or execution. The pagination support and project filtering are read-only parameters.
Attacks that exploit this kind of access
List existing E2E test scenarios saved in Assert. Use this to audit coverage before generating new tests. Supports pagination. Project filtering is reserved but not currently enforced by the API. It is categorised as a Read tool in the Assert MCP Server, which means it retrieves data without modifying state.
Register the Assert MCP server in PolicyLayer and add a rule for assert_list: 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 Assert. Nothing to install.
assert_list 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 assert_list 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 assert_list. 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.
assert_list is provided by the Assert MCP server (pixel-funnel/assert-click-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 →