Tests if the target URL (http://localhost) is accessible
AI agents call test_connection to retrieve information from MCP Login Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple connectivity check to determine if a local service is reachable. It retrieves status information with no side effects, no code execution, and no data modification. The operation is informational only, making it a Read category action with low severity since it poses minimal risk if misused—it can only confirm or deny accessibility of localhost.
From the tool's definition Tool name 'test_connection' and description 'Tests if the target URL (http://localhost) is accessible' indicate a read-only operation that queries connectivity status without modifying, executing code, or affecting data.
Attacks that exploit this kind of access
Tests if the target URL (http://localhost) is accessible. It is categorised as a Read tool in the MCP Login Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Login Server 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 MCP Login Server. 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 MCP Login Server MCP server (nieperdragon/custom_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
test_connection is one line of MCP Login Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →