AI agents call check_doc_ingested 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 information about document ingestion status without creating, modifying, deleting, or executing external operations. It is a query/verification operation with no side effects, fitting the Read category. Severity is low because misuse would only expose whether documents exist in the system, not sensitive content retrieval itself.
From the tool's definition Tool name 'check_doc_ingested' indicates a status check or verification operation. In the context of a RAG server with sibling tools like 'process_directory' and 'process_single_document', this tool appears to query whether a document has been ingested into…
Documented attack patterns abuse exactly the kind of access check_doc_ingested 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 check_doc_ingested:
{
"version": "1",
"default": "deny",
"tools": {
"check_doc_ingested": {}
}
}check_doc_ingested 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.
check_doc_ingested. 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 check_doc_ingested: 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.
check_doc_ingested 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 check_doc_ingested 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 check_doc_ingested. 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.
check_doc_ingested is provided by the RAG Anything MCP Server MCP server (jesse-merhi/rag-anything-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.
7 RAG Anything MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.