AI agents invoke iac_mcp_send_keystroke to trigger actions in Iac. 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.
Sending keystrokes to applications is an Execute-level action because it triggers arbitrary operations within the target application depending on what key/modifier combination is sent. Keystrokes can trigger any application function including saving, deleting, submitting forms, executing commands (e.g., Cmd+Q to quit, Cmd+A+Delete to delete all, etc.).
From the tool's definition Send a keystroke to an application with optional modifier keys
Attacks that exploit this kind of access
Send a keystroke to an application with optional modifier keys. Usage: Specify the app, key to press, and optional modifiers. Examples: - app:. It is categorised as a Execute tool in the Iac MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Iac MCP server in PolicyLayer and add a rule for iac_mcp_send_keystroke: 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 Iac. Nothing to install.
iac_mcp_send_keystroke 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 iac_mcp_send_keystroke 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 iac_mcp_send_keystroke. 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.
iac_mcp_send_keystroke is provided by the Iac MCP server (jsavin/iac-mcp). 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 →