create_server_config · Remote Terminal MCP: Risk & Policy

WHAT IT DOES

What create_server_config does on Remote Terminal MCP

AI agents use create_server_config to create or update resources in Remote Terminal MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Remote Terminal MCP environment.

WHY IT NEEDS A POLICY

Why create_server_config needs a policy

This tool creates a new server configuration, which is a reversible write operation—configurations can be modified or deleted. While it doesn't execute commands directly, misconfiguration could lead to security issues (wrong credentials, unintended server targets). However, it's Write rather than Execute because the act of creating config is data creation, not command execution.

From the tool's definition Tool description: 'Create a new server configuration'. The tool creates new configuration data that would be stored and used for subsequent server connections. The server context indicates this is part of remote SSH connection management.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_server_config Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_server_config": {
      "limits": [
        {
          "counter": "create_server_config_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 MCP, so you can run agents against it safely.

FAQ

Questions about create_server_config

What does the create_server_config tool do? +

Create a new server configuration. It is categorised as a Write tool in the Remote Terminal MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_server_config? +

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

What risk level is create_server_config? +

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

Can I rate-limit create_server_config? +

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

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

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