Terminate a PTY session. Future calls using the same session_id are rejected.
AI agents use terminate to create or update resources in PiloTY — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PiloTY environment.
An AI agent can call terminate faster than any human can review — one bad instruction and it creates or modifies resources in PiloTY by the hundred, each call as confident as the last.
Documented attack patterns abuse exactly the kind of access terminate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PiloTY, and nothing reaches the server without passing your rules. This is the rule we recommend for terminate:
{
"version": "1",
"default": "deny",
"tools": {
"terminate": {
"limits": [
{
"counter": "terminate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}terminate stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Terminate a PTY session. Future calls using the same session_id are rejected. It is categorised as a Write tool in the PiloTY MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PiloTY MCP server in PolicyLayer and add a rule for terminate: 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 PiloTY. Nothing to install.
terminate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the terminate 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 terminate. 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.
terminate is provided by the PiloTY MCP server (yiwenlu66/piloty). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 PiloTY tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
17 PiloTY tools catalogued and risk-classified — across an index of 42,500+ MCP servers.