expandPercyVisualTesting
AI agents call expandPercyVisualTesting as a supporting operation in BrowserStack workflows.
The description is empty, so the tool's behavior cannot be determined from it. The name suggests it relates to Percy visual testing expansion (likely a Write or Execute operation adding/configuring Percy visual testing steps), but without a description, confidence is very low. Based on sibling tools like 'addPercySnapshotCommands', it likely modifies test configurations (Write), but this is speculative.
From the tool's definition Tool name is 'expandPercyVisualTesting'; description is empty and uninformative.
Attacks that exploit this kind of access
expandPercyVisualTesting. It is categorised as a Other tool in the BrowserStack MCP Server, which means it performs auxiliary operations.
Register the BrowserStack MCP server in PolicyLayer and add a rule for expandPercyVisualTesting: 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.
expandPercyVisualTesting is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the expandPercyVisualTesting 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 expandPercyVisualTesting. 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.
expandPercyVisualTesting 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.