Low Risk

get_server_info

获取服务器信息

How to control get_server_info ↓

AI agents call get_server_info 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.

Low Risk

This tool retrieves or queries server metadata/information without modifying, executing operations on, or deleting any data. It is a straightforward information retrieval operation, classified as Read with low severity since exposing server information has minimal blast radius in the context of document manipulation.

From the tool's definition Tool name 'get_server_info' and description '获取服务器信息' (Get server information) indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_server_info 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 get_server_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_server_info": {}
  }
}

get_server_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Docx_MCP_cj — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_server_info tool do? +

获取服务器信息. It is categorised as a Read tool in the Docx_MCP_cj MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_server_info? +

Register the Docx_MCP_cj MCP server in PolicyLayer and add a rule for get_server_info: 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.

What risk level is get_server_info? +

get_server_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_server_info? +

Yes. Add a rate_limit block to the get_server_info 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.

How do I block get_server_info completely? +

Set action: deny in the PolicyLayer policy for get_server_info. 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.

What MCP server provides get_server_info? +

get_server_info 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.

Enforce policy on every Docx_MCP_cj tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.