safari_setup_check
Reports whether Safari is ready for interactive tools (safari_click, safari_type, safari_evaluate_js). Returns setup instructions if JavaScript from Apple Events is not enabled.
This record as markdown: /tools/com-local-mcp-local-mcp/safari-setup-check.md
What safari_setup_check does on Local
AI agents call safari_setup_check to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why safari_setup_check is rated Low
This tool only checks and reports the current configuration state of Safari. It performs a read/diagnostic operation with no side effects, no data modification, and no execution of user-supplied code.
From the tool's definition 'Reports whether Safari is ready' and 'Returns setup instructions if JavaScript from Apple Events is not enabled'
Attacks that exploit this kind of access
The rule that runs safari_setup_check 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_setup_check, this is the rule to start with:
safari_setup_check is read-only, so it stays allowed. 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_setup_check call is checked against it from then on.
Questions about safari_setup_check
Reports whether Safari is ready for interactive tools (safari_click, safari_type, safari_evaluate_js). Returns setup instructions if JavaScript from Apple Events is not enabled. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
Register the Local MCP server in PolicyLayer and add a rule for safari_setup_check: 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_setup_check 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 safari_setup_check 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_setup_check. 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_setup_check 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.
This server
Across the catalogue