New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

servers_test_connectivity

Run servers.test-connectivity through the Appaloft application operation catalog. Shared with CLI and HTTP/API.

SERVERAppaloft SOURCE@appaloft/mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/appaloft-mcp/servers-test-connectivity.md

What servers_test_connectivity does on Appaloft

AI agents invoke servers_test_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_connectivity is rated High

The tool executes a connectivity test operation against servers. While it is likely read-only in nature (checking network reachability), it triggers an external operation whose effects depend on arguments (which server to probe). This places it in Execute rather than Read. Severity is medium because probing arbitrary servers could reveal network topology or be used to port-scan internal infrastructure.

From the tool's definition 'Run servers.test-connectivity' — the word 'Run' indicates execution of an operation, specifically a connectivity test against servers

Questions about servers_test_connectivity

What does the servers_test_connectivity tool do? +

Run servers.test-connectivity through the Appaloft application operation catalog. Shared with CLI and 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.

How do I enforce a policy on servers_test_connectivity? +

Register the Appaloft MCP server in PolicyLayer and add a rule for servers_test_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.

What risk level is servers_test_connectivity? +

servers_test_connectivity is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit servers_test_connectivity? +

Yes. Add a rate_limit block to the servers_test_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.

How do I block servers_test_connectivity completely? +

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

What MCP server provides servers_test_connectivity? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Appaloft's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.