browser_mock_route
A execute tool on the Looking Glass MCP server.
This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/browser-mock-route.md
What browser_mock_route does on Looking Glass
AI agents invoke browser_mock_route to trigger actions in Looking Glass. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | — | Response body (default: {}) |
status | number | — | HTTP status code (default: 200) |
urlPattern | string | Yes | URL pattern to mock (e.g., /api/users) |
contentType | string | — | Content-Type header (default: application/json) |
Parameters from the server's own tool schema.
Why browser_mock_route is rated High
Based on the name, this tool likely intercepts and mocks browser network requests/routes, which is an Execute-level action as it modifies the browser's network behavior and can affect external operations. However, the empty description significantly reduces confidence in this classification.
From the tool's definition Tool name 'browser_mock_route' suggests intercepting/mocking browser network routes, which would execute browser-level network manipulation. Description is empty, lowering confidence.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs browser_mock_route 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_mock_route, this is the rule to start with:
browser_mock_route stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Looking Glass, apply this rule, and every browser_mock_route call is checked against it from then on.
Questions about browser_mock_route
browser_mock_route is a execute tool on the Looking Glass MCP server. It is categorised as a Execute tool in the Looking Glass MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
browser_mock_route accepts 4 parameters: body, status, urlPattern, contentType. Required: urlPattern. The full parameter table on this page comes from the server's own tool schema.
Register the Looking Glass MCP server in PolicyLayer and add a rule for browser_mock_route: 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 Looking Glass. Nothing to install.
browser_mock_route is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the browser_mock_route 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 browser_mock_route. 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.
browser_mock_route is provided by the Looking Glass MCP server (looking-glass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Looking Glass, and thousands of servers like it.
Across the catalogue