测试API连接状态
AI agents call test_api_connection to retrieve information from Zhipu AI Image Generation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a connectivity diagnostic tool that only verifies whether the API can be reached and is operational. It has no side effects, does not retrieve sensitive data, does not modify resources, and does not execute external operations. It is a read-only health check, making it the lowest severity category.
From the tool's definition Tool named 'test_api_connection' with description '测试API连接状态' (Chinese: 'Test API connection status'). The function performs a diagnostic check of API connectivity without retrieving, modifying, or executing operations on actual data or external systems.
Attacks that exploit this kind of access
测试API连接状态. It is categorised as a Read tool in the Zhipu AI Image Generation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zhipu AI Image Generation MCP Server MCP server in PolicyLayer and add a rule for test_api_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 Zhipu AI Image Generation MCP Server. Nothing to install.
test_api_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_api_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_api_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_api_connection is provided by the Zhipu AI Image Generation MCP Server MCP server (nanguangchou/zhipu_image_mcp). 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 →