web_type
Types text into a form field (input/textarea) on the current page. target is a CSS selector or the field's visible label/placeholder. Does NOT submit — use web_click on the submit button afterwards (that step is gated).
This record as markdown: /tools/com-local-mcp-local-mcp/web-type.md
What web_type does on Local
AI agents use web_type to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | The text to type. |
target | string | Yes | CSS selector or visible label/placeholder of the field. |
session | string | — | Session name (default 'default'). |
Parameters from the server's own tool schema.
Why web_type is rated Medium
The tool creates or modifies data in web forms non-destructively and does not execute commands or delete data. While it can input sensitive information (e.g., credentials, financial details) depending on context, the tool itself is a Write primitive that generates reversible changes.
From the tool's definition Tool description states it 'Types text into a form field (input/textarea) on the current page' and explicitly notes 'Does NOT submit' — this is data entry that modifies form state reversibly.
Attacks that exploit this kind of access
The rule that runs web_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 web_type, this is the rule to start with:
web_type stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 web_type call is checked against it from then on.
Questions about web_type
Types text into a form field (input/textarea) on the current page. target is a CSS selector or the field's visible label/placeholder. Does NOT submit — use web_click on the submit button afterwards (that step is gated). It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
web_type accepts 3 parameters: text, target, session. Required: text, target. 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 web_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.
web_type is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the web_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 web_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.
web_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.
This server
Across the catalogue