Test tool to verify MCP server is working.
AI agents call test_connection to retrieve information from WHOOP MCP Server for Poke without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a health-check or connectivity verification tool that merely confirms the server is operational. It retrieves status information with no side effects, making it a Read operation. The minimal scope and lack of access to sensitive user data make severity low. High confidence due to clear diagnostic purpose.
From the tool's definition Tool name 'test_connection' and description 'Test tool to verify MCP server is working' indicate a diagnostic operation that reads server status without modifying data or triggering external operations.
Attacks that exploit this kind of access
Test tool to verify MCP server is working. It is categorised as a Read tool in the WHOOP MCP Server for Poke MCP Server, which means it retrieves data without modifying state.
Register the WHOOP MCP Server for Poke MCP server in PolicyLayer and add a rule for test_connection: 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 WHOOP MCP Server for Poke. Nothing to install.
test_connection 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 test_connection 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_connection. 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_connection is provided by the WHOOP MCP Server for Poke MCP server (kabirrgrover/whoop-mcp-poke). 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 →