# chrome_fill_input

Fill text into an input field

Agent View of the PolicyLayer registry record for `chrome_fill_input`. HTML page: https://policylayer.com/tools/2019-02-18-mcx/chrome-fill-input

## Facts

- Tool: `chrome_fill_input`
- Server: Chrome Feedback (`2019-02-18/mcx`) — https://policylayer.com/tools/2019-02-18-mcx.md
- Homepage: https://github.com/2019-02-18/MCX
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "chrome_fill_input",
    "arguments": {}
  }
}
```

## Why chrome_fill_input is rated High

Filling an input field is a browser action that modifies the state of a web page element and can trigger form validation, event listeners, or autofill behaviors. It falls under Execute as it interacts with external browser operations whose effects depend on what field is targeted and what content is entered. It spans Write but Execute is more appropriate given it's a browser automation action.

From the tool's own definition: "Fill text into an input field"

## Use case

AI agents invoke chrome_fill_input to trigger actions in Chrome Feedback. 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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Chrome Feedback:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "chrome_fill_input": {
      "limits": [
        {
          "counter": "chrome_fill_input_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Chrome Feedback (15)

- `chrome_clear_feedback_history` — Destructive — https://policylayer.com/tools/2019-02-18-mcx/chrome-clear-feedback-history.md
- `chrome_click_element` — Execute — https://policylayer.com/tools/2019-02-18-mcx/chrome-click-element.md
- `chrome_execute_script` — Execute — https://policylayer.com/tools/2019-02-18-mcx/chrome-execute-script.md
- `chrome_interact_element` — Execute — https://policylayer.com/tools/2019-02-18-mcx/chrome-interact-element.md
- `chrome_navigate_to_url` — Execute — https://policylayer.com/tools/2019-02-18-mcx/chrome-navigate-to-url.md
- `chrome_wait_for_element` — Execute — https://policylayer.com/tools/2019-02-18-mcx/chrome-wait-for-element.md
- `chrome_analyze_form_structure` — Read — https://policylayer.com/tools/2019-02-18-mcx/chrome-analyze-form-structure.md
- `chrome_extract_content` — Read — https://policylayer.com/tools/2019-02-18-mcx/chrome-extract-content.md
- `chrome_get_extension_status` — Read — https://policylayer.com/tools/2019-02-18-mcx/chrome-get-extension-status.md
- `chrome_get_feedback_history` — Read — https://policylayer.com/tools/2019-02-18-mcx/chrome-get-feedback-history.md
- `chrome_get_page_info` — Read — https://policylayer.com/tools/2019-02-18-mcx/chrome-get-page-info.md
- `chrome_interactive_feedback` — Read — https://policylayer.com/tools/2019-02-18-mcx/chrome-interactive-feedback.md
- `chrome_smart_locate_element` — Read — https://policylayer.com/tools/2019-02-18-mcx/chrome-smart-locate-element.md
- `chrome_take_screenshot` — Read — https://policylayer.com/tools/2019-02-18-mcx/chrome-take-screenshot.md
- `chrome_fill_form` — Write — https://policylayer.com/tools/2019-02-18-mcx/chrome-fill-form.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=2019-02-18-mcx · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/2019-02-18-mcx