Execute multi-line script on remote host. Script is written to temp file then executed, completely avoiding bash escaping and encoding issues. Ideal for complex scripts with variables/template strings/unicode.
AI agents invoke remote_script to trigger actions in Mcp Remote Agent. 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.
This tool executes arbitrary multi-line scripts on remote hosts, which is a classic Execute operation. The severity is high because an AI agent with access to this tool could run any command with the permissions of the remote process, potentially compromising systems, exfiltrating data, or causing operational damage. The confidence is high because the description unambiguously describes script execution.
From the tool's definition Tool description explicitly states "Execute multi-line script on remote host" and "written to temp file then executed". This directly performs arbitrary code execution on a remote Linux server.
Attacks that exploit this kind of access
Execute multi-line script on remote host. Script is written to temp file then executed, completely avoiding bash escaping and encoding issues. Ideal for complex scripts with variables/template strings/unicode. It is categorised as a Execute tool in the Mcp Remote Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Remote Agent MCP server in PolicyLayer and add a rule for remote_script: 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 Mcp Remote Agent. Nothing to install.
remote_script 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 remote_script 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 remote_script. 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.
remote_script is provided by the Mcp Remote Agent MCP server (knownothing20/agentport). 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 →