browser_list_mocks

What browser_list_mocks does on Looking Glass

AI agents call browser_list_mocks to retrieve information from Looking Glass without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why browser_list_mocks is rated Low

The 'list' prefix indicates data retrieval without modification. In the context of a browser automation tool, listing mocks would retrieve mock configuration state for inspection—a read operation. No side effects are implied by the name alone. Severity is low because listing mock objects poses minimal risk if misused; an agent could only view existing mock state, not modify application behavior or cause damage.

From the tool's definition Tool name 'browser_list_mocks' suggests querying or enumerating mock objects; 'list' is a typical Read operation pattern. Description is empty, which reduces confidence.

The rule that runs browser_list_mocks safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Looking Glass, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_list_mocks, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_list_mocks": {}
  }
}

Questions about browser_list_mocks