Type text at the current cursor position on the VM. Use to enter text in a focused GUI field; for terminal/shell input prefer
AI agents invoke orgo_type to trigger actions in Orgo 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.
This tool executes an action on a virtual machine by simulating keyboard input at the current cursor position. It triggers external operations on the remote VM (GUI interaction), and depending on what text is typed, could have significant side effects (e.g., typing commands into a terminal, entering data into forms, or triggering UI actions).
From the tool's definition Type text at the current cursor position on the VM. Use to enter text in a focused GUI field; for terminal/shell input prefer
Documented attack patterns abuse exactly the kind of access orgo_type gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Orgo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for orgo_type:
{
"version": "1",
"default": "deny",
"tools": {
"orgo_type": {
"limits": [
{
"counter": "orgo_type_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} orgo_type 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.
Free to start. No card required.
Type text at the current cursor position on the VM. Use to enter text in a focused GUI field; for terminal/shell input prefer. It is categorised as a Execute tool in the Orgo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Orgo MCP Server MCP server in PolicyLayer and add a rule for orgo_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 Orgo MCP Server. Nothing to install.
orgo_type 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 orgo_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 orgo_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.
orgo_type is provided by the Orgo MCP Server MCP server (nickvasilescu/orgo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Orgo MCP Server, 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.
28 Orgo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.