check_server_connectivity
Check server connectivity and network status
This record as markdown: /tools/caravanglory-cocos-mcp-server/check-server-connectivity.md
What check_server_connectivity does on Cocos
AI agents call check_server_connectivity to retrieve information from Cocos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_server_connectivity is rated Low
This tool performs a read-only diagnostic check of network connectivity and server status. It retrieves information about the current state of connections but does not create, modify, delete, or execute any operations. The tool has no side effects and presents minimal risk if invoked by an AI agent, making it a straightforward Read category classification with low severity.
From the tool's definition Tool name 'check_server_connectivity' and description 'Check server connectivity and network status' indicate a diagnostic query operation that retrieves status information without modifying state or triggering external operations.
Attacks that exploit this kind of access
The rule that runs check_server_connectivity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cocos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_server_connectivity, this is the rule to start with:
check_server_connectivity is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cocos, apply this rule, and every check_server_connectivity call is checked against it from then on.
Questions about check_server_connectivity
Check server connectivity and network status. It is categorised as a Read tool in the Cocos MCP Server, which means it retrieves data without modifying state.
Register the Cocos MCP server in PolicyLayer and add a rule for check_server_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 Cocos. Nothing to install.
check_server_connectivity is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_server_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 check_server_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.
check_server_connectivity is provided by the Cocos MCP server (caravanglory/cocos-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cocos, and thousands of servers like it.
This server
Across the catalogue