Type a sensitive vault field value using keyboard events. The target field must be focused. The secret never appears in the agent context.
AI agents invoke blind_type to trigger actions in Shellgate. 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 triggers keyboard input events (an external operation/browser action) to inject sensitive credential values into a focused field. It executes UI automation rather than simply reading or writing data, and misuse could lead to credential injection into unintended fields.
From the tool's definition 'Type a sensitive vault field value using keyboard events. The target field must be focused.'
Documented attack patterns abuse exactly the kind of access blind_type gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Shellgate, and nothing reaches the server without passing your rules. This is the rule we recommend for blind_type:
{
"version": "1",
"default": "deny",
"tools": {
"blind_type": {
"limits": [
{
"counter": "blind_type_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}blind_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 a sensitive vault field value using keyboard events. The target field must be focused. The secret never appears in the agent context. It is categorised as a Execute tool in the Shellgate MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Shellgate MCP server in PolicyLayer and add a rule for blind_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 Shellgate. Nothing to install.
blind_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 blind_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 blind_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.
blind_type is provided by the Shellgate MCP server (matthiastjong/shellgate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Shellgate, 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.
31 Shellgate tools catalogued and risk-classified — across an index of 43,000+ MCP servers.