Medium Risk

terminal_send_key

Send a key to the terminal.

Part of the Terminal server.

terminal_send_key can modify Terminal data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE TERMINAL →

Free to start. No card required.

AI agents use terminal_send_key to create or modify resources in Terminal. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call terminal_send_key repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Terminal.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "terminal_send_key": {
      "limits": [
        {
          "counter": "terminal_send_key_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Terminal policy for all 15 tools.

Get this rule live on your own Terminal server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TERMINAL →

View all 15 tools →

These attack patterns abuse exactly the kind of access terminal_send_key gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so terminal_send_key only ever does what you allow.

SECURE TERMINAL →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the terminal_send_key tool do? +

Send a key to the terminal.. It is categorised as a Write tool in the Terminal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on terminal_send_key? +

Register the Terminal MCP server in PolicyLayer and add a rule for terminal_send_key: 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 Terminal. Nothing to install.

What risk level is terminal_send_key? +

terminal_send_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit terminal_send_key? +

Yes. Add a rate_limit block to the terminal_send_key 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.

How do I block terminal_send_key completely? +

Set action: deny in the PolicyLayer policy for terminal_send_key. 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.

What MCP server provides terminal_send_key? +

terminal_send_key is provided by the Terminal MCP server (pungggi/smart-terminal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Terminal tool call.

Deterministic rules across all 15 Terminal tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.