fill-input

A execute tool on the AdsPower LocalAPI MCP server.

SERVERAdsPower LocalAPI MCP Server SOURCEadspower/adspower-browser

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adspower-adspower-browser/fill-input.md

WHAT IT DOES

What fill-input does on AdsPower LocalAPI MCP Server

AI agents invoke fill-input to trigger actions in AdsPower LocalAPI MCP Server. 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.

RISK

Why fill-input is rated High

Based on the server context (browser automation/control) and sibling tools like 'click-element', 'fill-input' almost certainly fills form fields in a browser session. This is a browser action/execution operation. The description is empty, lowering confidence. Severity is medium because filling inputs could submit forms, enter credentials, or trigger actions depending on what is filled.

From the tool's definition Tool name 'fill-input' on a browser automation server that 'enabling LLMs to interact with AdsPower browser LocalAPI' with sibling tools like 'click-element' and 'connect-browser-with-ws'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fill-input safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AdsPower LocalAPI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fill-input, this is the rule to start with:

fill-input Rate-limited

fill-input 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fill-input": {
      "limits": [
        {
          "counter": "fill-input_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AdsPower LocalAPI MCP Server, apply this rule, and every fill-input call is checked against it from then on.

FAQ

Questions about fill-input

What does the fill-input tool do? +

fill-input is a execute tool on the AdsPower LocalAPI MCP Server MCP server. It is categorised as a Execute tool in the AdsPower LocalAPI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on fill-input? +

Register the AdsPower LocalAPI MCP Server MCP server in PolicyLayer and add a rule for fill-input: 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 AdsPower LocalAPI MCP Server. Nothing to install.

What risk level is fill-input? +

fill-input is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit fill-input? +

Yes. Add a rate_limit block to the fill-input 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.

How do I block fill-input completely? +

Set action: deny in the PolicyLayer policy for fill-input. 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.

What MCP server provides fill-input? +

fill-input is provided by the AdsPower LocalAPI MCP Server MCP server (adspower/adspower-browser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on AdsPower LocalAPI MCP Server, and thousands of servers like it.

This server

All 47 AdsPower LocalAPI MCP Server tools → High-risk tools on this server →

Across the catalogue

browser_fill on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →