AI agents invoke type_text to trigger actions in Pl. 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.
Typing text into a focused element is a browser/UI action that triggers external operations with context-dependent effects. It could fill forms, trigger search queries, or modify data in the application. Since it drives an external UI (Platforma Desktop), it falls under Execute rather than Write, as the side effects depend heavily on what element is focused and what text is typed.
From the tool's definition 'Type text into the currently focused element' — triggers a UI interaction (keyboard input) on an external application element, whose effect depends on the target element and text content.
Attacks that exploit this kind of access
Type text into the currently focused element. It is categorised as a Execute tool in the Pl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pl MCP server in PolicyLayer and add a rule for type_text: 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 Pl. Nothing to install.
type_text is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the type_text 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_text. 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_text is provided by the Pl MCP server (@milaboratories/pl-mcp-server). 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 →