test_mcp_server
Test connectivity to an MCP server. Sends a live check and returns success, response time, HTTP status, and any error; use this before changing configuration or when diagnosing reachability.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/test-mcp-server.md
What test_mcp_server does on Portkey Admin
AI agents invoke test_mcp_server to trigger actions in Portkey Admin. 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 test_mcp_server is rated High
This tool executes a live network connectivity check against an external MCP server. It triggers an outbound HTTP request and returns status/response time. While read-like in intent (diagnosing reachability), it actively executes an external operation whose effects depend on the target argument, fitting Execute.
From the tool's definition 'Test connectivity to an MCP server. Sends a live check' — actively sends a network request to an external MCP server
Attacks that exploit this kind of access
The rule that runs test_mcp_server safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Portkey Admin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For test_mcp_server, this is the rule to start with:
test_mcp_server 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 Portkey Admin, apply this rule, and every test_mcp_server call is checked against it from then on.
Questions about test_mcp_server
Test connectivity to an MCP server. Sends a live check and returns success, response time, HTTP status, and any error; use this before changing configuration or when diagnosing reachability. It is categorised as a Execute tool in the Portkey Admin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for test_mcp_server: 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 Portkey Admin. Nothing to install.
test_mcp_server 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 test_mcp_server 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_mcp_server. 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_mcp_server is provided by the Portkey Admin MCP server (codeswhat/portkey-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Portkey Admin, and thousands of servers like it.
Across the catalogue