puppeteer_fill

// WHEN AI AGENTS USE THIS TOOL

AI agents use puppeteer_fill to create or modify resources in Puppeteer. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON PUPPETEER_FILL

Without a policy, an AI agent could call puppeteer_fill repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Puppeteer.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

puppeteer.yaml

tools:
  puppeteer_fill:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Puppeteer policy for all 7 tools.

// DETAILS

Tool Name puppeteer_fill

Category Write

MCP Server Puppeteer MCP Server

Risk Level Medium

// MORE PUPPETEER TOOLS

Execute puppeteer_evaluate Execute puppeteer_navigate Write puppeteer_click Write puppeteer_hover Write puppeteer_select Read puppeteer_screenshot

// WHAT CAN GO WRONG

Agents calling write-class tools like puppeteer_fill have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the puppeteer_fill tool do? +

Fill out an input field. It is categorised as a Write tool in the Puppeteer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on puppeteer_fill? +

Add a rule in your Intercept YAML policy under the tools section for puppeteer_fill. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Puppeteer MCP server.

What risk level is puppeteer_fill? +

puppeteer_fill is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit puppeteer_fill? +

Yes. Add a rate_limit block to the puppeteer_fill rule in your Intercept 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 puppeteer_fill completely? +

Set action: deny in the Intercept policy for puppeteer_fill. 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 puppeteer_fill? +

puppeteer_fill is provided by the Puppeteer MCP server (@modelcontextprotocol/server-puppeteer). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Puppeteer