Create an authentication configuration for accessibility scans. Supports both form-based and basic authentication.
Free to start. No card required.
AI agents use createAccessibilityAuthConfig to create or update resources in BrowserStack — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BrowserStack environment.
This tool creates a new authentication configuration object, which is a reversible write operation. It does not execute arbitrary code, delete data, move money, or retrieve information.
From the tool's definition The tool name is 'createAccessibilityAuthConfig' and description states 'Create an authentication configuration for accessibility scans. Supports both form-based and basic authentication.' The verb 'Create' indicates data creation.
Documented attack patterns abuse exactly the kind of access createAccessibilityAuthConfig gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BrowserStack, and nothing reaches the server without passing your rules. This is the rule we recommend for createAccessibilityAuthConfig:
{
"version": "1",
"default": "deny",
"tools": {
"createAccessibilityAuthConfig": {
"limits": [
{
"counter": "createaccessibilityauthconfig_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createAccessibilityAuthConfig stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create an authentication configuration for accessibility scans. Supports both form-based and basic authentication. It is categorised as a Write tool in the BrowserStack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the BrowserStack MCP server in PolicyLayer and add a rule for createAccessibilityAuthConfig: 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.
createAccessibilityAuthConfig is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the createAccessibilityAuthConfig 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 createAccessibilityAuthConfig. 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.
createAccessibilityAuthConfig 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.
Start from BrowserStack, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
43 BrowserStack tools catalogued and risk-classified — across an index of 43,000+ MCP servers.