Type text into an input element
AI agents use type to create or update resources in Chrome Profile MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Chrome Profile MCP Server environment.
The tool creates or modifies data by inputting text into form fields. While reversible (text can be cleared/overwritten), it constitutes a write operation. Severity is medium rather than high because the impact is confined to the current browser session and web page state, though it could be used to submit sensitive information or modify important form data depending on the target form.
From the tool's definition Tool description states 'Type text into an input element' - this modifies input field state and creates/updates data within the browser document.
Attacks that exploit this kind of access
Type text into an input element. It is categorised as a Write tool in the Chrome Profile MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Chrome Profile MCP Server 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 Profile MCP Server. 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 Profile MCP Server MCP server (nghiahsgs/vibe-mcp-chrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →