safari_query_selector_all
Runs document.querySelectorAll in the current Safari tab and returns a compact summary of each match.
This record as markdown: /tools/com-local-mcp-local-mcp/safari-query-selector-all.md
What safari_query_selector_all does on Local
AI agents invoke safari_query_selector_all to trigger actions in Local. 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 |
|---|---|---|---|
limit | integer | — | |
selector | string | Yes |
Parameters from the server's own tool schema.
Why safari_query_selector_all is rated High
The tool executes JavaScript (document.querySelectorAll) within a live Safari browser tab. While querySelectorAll itself is primarily a read operation, executing arbitrary JavaScript in a browser context is an Execute-category action with potential for side effects depending on arguments and page state. The blast radius is medium as it could expose sensitive page content or be chained with other actions.
From the tool's definition Runs document.querySelectorAll in the current Safari tab
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs safari_query_selector_all safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For safari_query_selector_all, this is the rule to start with:
safari_query_selector_all 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 Local, apply this rule, and every safari_query_selector_all call is checked against it from then on.
Questions about safari_query_selector_all
Runs document.querySelectorAll in the current Safari tab and returns a compact summary of each match. It is categorised as a Execute tool in the Local MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
safari_query_selector_all accepts 2 parameters: limit, selector. Required: selector. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for safari_query_selector_all: 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 Local. Nothing to install.
safari_query_selector_all 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 safari_query_selector_all 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 safari_query_selector_all. 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.
safari_query_selector_all is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
Across the catalogue