fetch_node_detail_info
AI agents call fetch_node_detail_info to retrieve information from ShowDoc MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool fetches node detail information, which is a query/retrieval operation with no side effects. It integrates with ShowDoc's documentation system to retrieve details. The lack of description slightly lowers confidence, but the naming convention and surrounding context (other fetch_* tools on this server) strongly indicate this is a Read operation.
From the tool's definition Tool name 'fetch_node_detail_info' and server context indicate retrieval of documentation/node details from ShowDoc. No description provided, but naming pattern and sibling tools (fetch_showdoc_apis, fetch_showdoc_node_tree) confirm read-only data retrieval.
Attacks that exploit this kind of access
fetch_node_detail_info. It is categorised as a Read tool in the ShowDoc MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ShowDoc MCP Server MCP server in PolicyLayer and add a rule for fetch_node_detail_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 ShowDoc MCP Server. Nothing to install.
fetch_node_detail_info 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 fetch_node_detail_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.
Set action: deny in the PolicyLayer policy for fetch_node_detail_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.
fetch_node_detail_info is provided by the ShowDoc MCP Server MCP server (yfcyfc123234/showdoc_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 →