AI agents use type to create or update resources in Chrome MCP Docker — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Chrome MCP Docker environment.
The 'type' tool writes/modifies data by entering text into input fields. This is reversible (text can be cleared), so it is Write rather than Destructive. It is not Read (no retrieval), Execute (no code/command execution), Financial, or Other.
From the tool's definition Tool description: 'Types text into an input field.' This modifies form input state, which is data creation/modification in the browser context.
Documented attack patterns abuse exactly the kind of access type gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Chrome MCP Docker, and nothing reaches the server without passing your rules. This is the rule we recommend for type:
{
"version": "1",
"default": "deny",
"tools": {
"type": {
"limits": [
{
"counter": "type_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Types text into an input field. It is categorised as a Write tool in the Chrome MCP Docker MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Chrome MCP Docker MCP server in PolicyLayer and add a rule for 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 Chrome MCP Docker. Nothing to install.
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 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 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.
type is provided by the Chrome MCP Docker MCP server (null-runner/chrome-mcp-docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Chrome MCP Docker, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Chrome MCP Docker tools catalogued and risk-classified — across an index of 43,000+ MCP servers.