Get knowledge graph configuration information.
AI agents call get_config_info to retrieve information from RAG-Anything MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration metadata about a knowledge graph. It performs a read-only query with no side effects, no code execution, no data modification, and no destructive operations. The blast radius of misuse is minimal—an attacker could only learn configuration details, which may have informational value but cannot directly compromise data integrity or trigger external operations.
From the tool's definition Tool name 'get_config_info' and description 'Get knowledge graph configuration information' indicate a retrieval operation with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access get_config_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RAG-Anything MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_config_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_config_info": {}
}
}get_config_info 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.
Get knowledge graph configuration information. It is categorised as a Read tool in the RAG-Anything MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RAG-Anything MCP Server MCP server in PolicyLayer and add a rule for get_config_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 RAG-Anything MCP Server. Nothing to install.
get_config_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 get_config_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 get_config_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.
get_config_info is provided by the RAG-Anything MCP Server MCP server (serkanyasr/rag-anythink-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from RAG-Anything MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 RAG-Anything MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.