Retrieve the actual Python source code for a function/class from the local Dagster repository using its GitHub documentation URL. Returns the complete implementation with surrounding context. For more control over the level of detail (signature only, class outline, methods list, or specific metho...
AI agents call get_source_code to retrieve information from RAG Document Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs semantic retrieval of source code from a local repository. It retrieves and returns data with no side effects—no modifications, deletions, or code execution. The function is purely informational, similar to viewing a file or querying documentation.
From the tool's definition Tool description states it 'Retrieve[s] the actual Python source code' and 'Returns the complete implementation', indicating a read-only retrieval operation. No modify, delete, or execute capabilities are mentioned.
Attacks that exploit this kind of access
Retrieve the actual Python source code for a function/class from the local Dagster repository using its GitHub documentation URL. Returns the complete implementation with surrounding context. For more control over the level of detail (signature only, class outline, methods list, or specific method extraction), use get_source_code_advanced instead. It is categorised as a Read tool in the RAG Document Server MCP Server, which means it retrieves data without modifying state.
Register the RAG Document Server MCP server in PolicyLayer and add a rule for get_source_code: 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 Document Server. Nothing to install.
get_source_code 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_source_code 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_source_code. 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_source_code is provided by the RAG Document Server MCP server (jaimeferj/mcp-rag-docs). 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 →