List test IDs from a BrowserStack Automate build, optionally filtered by status
AI agents call listTestIds to retrieve information from BrowserStack 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 test identifiers from an existing build, with optional filtering by status. It performs no data modification, deletion, execution, or financial operations. It is a straightforward read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'listTestIds' and description 'List test IDs from a BrowserStack Automate build, optionally filtered by status' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List test IDs from a BrowserStack Automate build, optionally filtered by status. It is categorised as a Read tool in the BrowserStack MCP Server, which means it retrieves data without modifying state.
Register the BrowserStack MCP server in PolicyLayer and add a rule for listTestIds: 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 BrowserStack. Nothing to install.
listTestIds 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 listTestIds 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 listTestIds. 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.
listTestIds is provided by the BrowserStack MCP server (browserstack/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.