start_conversation · Remote Terminal MCP: Risk & Policy

WHAT IT DOES

What start_conversation does on Remote Terminal

AI agents invoke start_conversation to trigger actions in Remote Terminal. 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.

WHY IT NEEDS A POLICY

Why start_conversation needs a policy

start_conversation triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_conversation Rate-limited

start_conversation 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_conversation": {
      "limits": [
        {
          "counter": "start_conversation_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Remote Terminal, so you can run agents against it safely.

FAQ

Questions about start_conversation

What does the start_conversation tool do? +

start_conversation. It is categorised as a Execute tool in the Remote Terminal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_conversation? +

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

What risk level is start_conversation? +

start_conversation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_conversation? +

Yes. Add a rate_limit block to the start_conversation 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 start_conversation completely? +

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

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