AI agents call list_sources to retrieve information from MCP-Ragdocs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about stored documentation sources without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal security impact; the only concern would be information disclosure about what documentation has been indexed, which is low severity.
From the tool's definition Tool name is 'list_sources' and description states it 'List all documentation sources currently stored' — a query operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_sources gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Ragdocs, and nothing reaches the server without passing your rules. This is the rule we recommend for list_sources:
{
"version": "1",
"default": "deny",
"tools": {
"list_sources": {}
}
}list_sources 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.
List all documentation sources currently stored. It is categorised as a Read tool in the MCP-Ragdocs MCP Server, which means it retrieves data without modifying state.
Register the MCP-Ragdocs MCP server in PolicyLayer and add a rule for list_sources: 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 MCP-Ragdocs. Nothing to install.
list_sources 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_sources 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_sources. 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_sources is provided by the MCP-Ragdocs MCP server (qpd-v/mcp-ragdocs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 MCP-Ragdocs tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 MCP-Ragdocs tools catalogued and risk-classified — across an index of 42,500+ MCP servers.