Launch interactive configuration wizard to set up a new server
AI agents use interactive_config_wizard 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.
This tool creates new server configurations, which is a write operation that modifies stored state. While configurations can be deleted or updated later (making it reversible rather than destructive), the tool's core function is to create/persist new data. Confidence is high because the description clearly indicates creation/setup.
From the tool's definition Tool description states 'set up a new server' and 'configuration wizard', which creates or modifies server configuration data.
Attacks that exploit this kind of access
Launch interactive configuration wizard to set up a new server. 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.
Register the Remote Terminal MCP server in PolicyLayer and add a rule for interactive_config_wizard: 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.
interactive_config_wizard 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 interactive_config_wizard 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 interactive_config_wizard. 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.
interactive_config_wizard 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.
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 →