List canonical Markdown documentation topics served by the MCP knowledge base.
AI agents call list_xgr_docs to retrieve information from XGR MCP Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists documentation topics from a knowledge base. It performs a read-only query operation with no side effects, no code execution, no data modification, and no financial impact. The blast radius of misuse is minimal—an AI could at worst retrieve documentation it shouldn't see, but cannot execute operations, modify blockchain state, or cause financial harm.
From the tool's definition Tool name 'list_xgr_docs' and description 'List canonical Markdown documentation topics' indicate retrieval/enumeration of documentation metadata with no modification or execution.
Attacks that exploit this kind of access
List canonical Markdown documentation topics served by the MCP knowledge base. It is categorised as a Read tool in the XGR MCP Gateway MCP Server, which means it retrieves data without modifying state.
Register the XGR MCP Gateway MCP server in PolicyLayer and add a rule for list_xgr_docs: 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 XGR MCP Gateway. Nothing to install.
list_xgr_docs 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 list_xgr_docs 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 list_xgr_docs. 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.
list_xgr_docs is provided by the XGR MCP Gateway MCP server (xgr-network/xgr-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 →