AI agents call test_connection to retrieve information from Browserless MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Testing a connection is a read-only diagnostic operation that queries the status of the Browserless service without triggering automation tasks, modifying data, or executing external commands. The tool has minimal blast radius—at worst, it could leak connection details or service availability information. It belongs in the Read category.
From the tool's definition Tool name 'test_connection' and description 'Test connection to Browserless instance' indicate a diagnostic check with no data modification, execution, or side effects. This is a health/connectivity verification operation.
Documented attack patterns abuse exactly the kind of access test_connection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Browserless MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for test_connection:
{
"version": "1",
"default": "deny",
"tools": {
"test_connection": {}
}
}test_connection is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Test connection to Browserless instance. It is categorised as a Read tool in the Browserless MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Browserless MCP Server MCP server in PolicyLayer and add a rule for test_connection: 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 Browserless MCP Server. Nothing to install.
test_connection 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 test_connection 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 test_connection. 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.
test_connection is provided by the Browserless MCP Server MCP server (lizzard-solutions/browserless-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Browserless MCP Server, 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.
16 Browserless MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.