Use this tool to debug failures in the last run of the test suite on BrowserStack. Use only when browserstack.yml file is present in the project root.
AI agents call getFailuresInLastRun 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 queries and retrieves historical test failure data for debugging purposes. It has no side effects—it does not create, modify, delete, or execute any operations. It is purely a read operation that fetches information from a previous test run.
From the tool's definition Tool name and description indicate retrieval/querying functionality: 'getFailuresInLastRun' retrieves failure data from a completed test run.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Use this tool to debug failures in the last run of the test suite on BrowserStack. Use only when browserstack.yml file is present in the project root. 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 getFailuresInLastRun: 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.
getFailuresInLastRun 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 getFailuresInLastRun 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 getFailuresInLastRun. 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.
getFailuresInLastRun 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.