safari_fill_form
Fills multiple form fields in one shot. Pass fields as a JSON object mapping CSS selector to value.
This record as markdown: /tools/com-local-mcp-local-mcp/safari-fill-form.md
What safari_fill_form does on Local
AI agents invoke safari_fill_form 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 |
|---|---|---|---|
fields | string | Yes |
Parameters from the server's own tool schema.
Why safari_fill_form is rated High
Filling form fields in a browser triggers interactions with live web forms that can submit data, authenticate users, or initiate actions on external services. The effect depends on which form is targeted and what values are injected, making this an Execute-class browser action with high blast radius if misused by an AI agent.
From the tool's definition Fills multiple form fields in one shot. Pass fields as a JSON object mapping CSS selector to value.
Attacks that exploit this kind of access
The rule that runs safari_fill_form 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_fill_form, this is the rule to start with:
safari_fill_form 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_fill_form call is checked against it from then on.
Questions about safari_fill_form
Fills multiple form fields in one shot. Pass fields as a JSON object mapping CSS selector to value. 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_fill_form accepts 1 parameter: fields. Required: fields. 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_fill_form: 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_fill_form 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_fill_form 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_fill_form. 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_fill_form 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