AI agents invoke pty_write to trigger actions in Pty. 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.
pty_write sends arbitrary input to an active pseudo-terminal session, which can drive any interactive CLI process. Since the server is designed to execute shell commands, run database migrations, and scaffold projects, writing to a PTY session effectively executes arbitrary commands in that shell. The blast radius is high because an AI agent could send destructive or privileged commands to any running process.
From the tool's definition Send input to a running PTY session... enables agents to autonomously spawn processes, read output, and send inputs for workflows like database migrations and project scaffolding
Attacks that exploit this kind of access
Send input to a running PTY session. Returns new output after the input is processed. Use press_enter to submit (default true). It is categorised as a Execute tool in the Pty MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pty MCP server in PolicyLayer and add a rule for pty_write: 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 Pty. Nothing to install.
pty_write 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 pty_write 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 pty_write. 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.
pty_write is provided by the Pty MCP server (reedm121/pty-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 →