test_host_connection_by_info
A execute tool on the 1Panel MCP server.
This record as markdown: /tools/eaveluo-1panel-mcp/test-host-connection-by-info.md
What test_host_connection_by_info does on 1Panel MCP Server
AI agents invoke test_host_connection_by_info to trigger actions in 1Panel MCP Server. 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 test_host_connection_by_info is rated High
This tool executes a live network connection test, which is an active external operation whose effects (network probing, authentication attempts) depend on the supplied arguments. It's not purely a read/query of stored data — it triggers an outbound connection. Severity is medium since misuse could probe unauthorized hosts or leak credentials, but it doesn't modify or destroy data.
From the tool's definition 'Test host connection by info' — actively initiates a network connection attempt to an external host using provided connection parameters
Attacks that exploit this kind of access
The rule that runs test_host_connection_by_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1Panel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For test_host_connection_by_info, this is the rule to start with:
test_host_connection_by_info 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.
The button opens the PolicyLayer dashboard: create your workspace, connect 1Panel MCP Server, apply this rule, and every test_host_connection_by_info call is checked against it from then on.
Questions about test_host_connection_by_info
test_host_connection_by_info is a execute tool on the 1Panel MCP Server MCP server. It is categorised as a Execute tool in the 1Panel MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 1Panel MCP Server MCP server in PolicyLayer and add a rule for test_host_connection_by_info: 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 1Panel MCP Server. Nothing to install.
test_host_connection_by_info 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 test_host_connection_by_info 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 test_host_connection_by_info. 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.
test_host_connection_by_info is provided by the 1Panel MCP Server MCP server (eaveluo/1panel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1Panel MCP Server, and thousands of servers like it.
Across the catalogue