safari_type
Sets the value of an input/textarea matching a CSS selector and fires input/change events.
This record as markdown: /tools/com-local-mcp-local-mcp/safari-type.md
What safari_type does on Local
AI agents invoke safari_type 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 |
|---|---|---|---|
clear | boolean | — | |
value | string | Yes | |
selector | string | Yes |
Parameters from the server's own tool schema.
Why safari_type is rated High
This tool programmatically sets input values and fires DOM events in Safari, which constitutes browser automation/execution. It can trigger reactive logic (onChange handlers, form submissions, etc.) depending on the target element, making it an Execute-category action. Misuse could lead to unintended form submissions or data entry in sensitive web contexts.
From the tool's definition Sets the value of an input/textarea matching a CSS selector and fires input/change events
Attacks that exploit this kind of access
The rule that runs safari_type 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_type, this is the rule to start with:
safari_type 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_type call is checked against it from then on.
Questions about safari_type
Sets the value of an input/textarea matching a CSS selector and fires input/change events. 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_type accepts 3 parameters: clear, value, selector. Required: value, 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_type: 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_type 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_type 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_type. 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_type 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