get_source_file
Retrieve the full content of a specific source file from the indexed directory.
This record as markdown: /tools/42research-dynamic-mcp/get-source-file.md
What get_source_file does on Dynamic MCP Server
AI agents call get_source_file to retrieve information from Dynamic MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_source_file is rated Low
This tool performs a read-only operation to retrieve source file content. It queries indexed data without modifying, deleting, or executing any code. The action is non-destructive and non-reversible. While the server as a whole deals with kernel debugging (which could be sensitive), this specific tool merely fetches file content for inspection, which is a Read operation.
From the tool's definition Tool name 'get_source_file' and description 'Retrieve the full content of a specific source file from the indexed directory' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs get_source_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dynamic MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_source_file, this is the rule to start with:
get_source_file is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Dynamic MCP Server, apply this rule, and every get_source_file call is checked against it from then on.
Questions about get_source_file
Retrieve the full content of a specific source file from the indexed directory. It is categorised as a Read tool in the Dynamic MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dynamic MCP Server MCP server in PolicyLayer and add a rule for get_source_file: 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 Dynamic MCP Server. Nothing to install.
get_source_file 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_file 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_file. 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_file is provided by the Dynamic MCP Server MCP server (42research/dynamic_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dynamic MCP Server, and thousands of servers like it.
This server
Across the catalogue