AI agents call test_connection to retrieve information from Docx_MCP_cj without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A connection test tool performs read-only verification of connectivity status without modifying, executing, or deleting any data. It has minimal blast radius—worst case, it provides diagnostic information about system state. This is a benign operational tool typical of API clients and integrations.
From the tool's definition Tool name 'test_connection' and description indicating a connection test operation. No data modification, deletion, or command execution is implied. The description '测试连接' (test connection in Chinese) confirms this is a diagnostic/verification operation.
Documented attack patterns abuse exactly the kind of access test_connection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Docx_MCP_cj, and nothing reaches the server without passing your rules. This is the rule we recommend for test_connection:
{
"version": "1",
"default": "deny",
"tools": {
"test_connection": {}
}
}test_connection is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
测试连接. It is categorised as a Read tool in the Docx_MCP_cj MCP Server, which means it retrieves data without modifying state.
Register the Docx_MCP_cj 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 Docx_MCP_cj. 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 Docx_MCP_cj MCP server (rockcj/docx_mcp_cj). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 54 Docx_MCP_cj tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
54 Docx_MCP_cj tools catalogued and risk-classified — across an index of 42,500+ MCP servers.