servers_test_draft_connectivity
Run servers.test-draft-connectivity through the Appaloft application operation catalog. Shared with HTTP/API.
This record as markdown: /tools/appaloft-mcp/servers-test-draft-connectivity.md
What servers_test_draft_connectivity does on Appaloft
AI agents invoke servers_test_draft_connectivity to trigger actions in Appaloft. 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 servers_test_draft_connectivity is rated High
The tool executes a connectivity test operation against a draft server, which involves actively initiating network connections or probes. This is an Execute action (triggering an external operation) rather than a simple Read. The severity is medium because misuse could probe internal infrastructure or reveal network topology, but it does not directly modify or destroy data.
From the tool's definition 'Run servers.test-draft-connectivity' — the word 'Run' indicates execution of an operation; 'test-draft-connectivity' suggests triggering an active connectivity check against a draft server configuration
Attacks that exploit this kind of access
The rule that runs servers_test_draft_connectivity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For servers_test_draft_connectivity, this is the rule to start with:
servers_test_draft_connectivity 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 Appaloft, apply this rule, and every servers_test_draft_connectivity call is checked against it from then on.
Questions about servers_test_draft_connectivity
Run servers.test-draft-connectivity through the Appaloft application operation catalog. Shared with HTTP/API. It is categorised as a Execute tool in the Appaloft MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Appaloft MCP server in PolicyLayer and add a rule for servers_test_draft_connectivity: 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 Appaloft. Nothing to install.
servers_test_draft_connectivity 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 servers_test_draft_connectivity 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 servers_test_draft_connectivity. 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.
servers_test_draft_connectivity is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
Across the catalogue