Get source context around a selected frame/thread for dump_id (uses source_path_map remap when provided at register_dump).
AI agents call get_source_context to retrieve information from DumpAnalysisMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and returns source code context around a specific frame or thread in a crash dump. It is purely a data retrieval operation with no writes, executions, or destructive actions. The source_path_map remapping is a read-time transformation, not a persistent change. Severity is low as it only exposes source code snippets.
From the tool's definition 'Get source context around a selected frame/thread' — retrieves source code context for display/analysis purposes only, no side effects
Documented attack patterns abuse exactly the kind of access get_source_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DumpAnalysisMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_source_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_source_context": {}
}
}get_source_context 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 source context around a selected frame/thread for dump_id (uses source_path_map remap when provided at register_dump). It is categorised as a Read tool in the DumpAnalysisMCP MCP Server, which means it retrieves data without modifying state.
Register the DumpAnalysis MCP server in PolicyLayer and add a rule for get_source_context: 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 DumpAnalysisMCP. Nothing to install.
get_source_context 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_context 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_context. 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_context is provided by the DumpAnalysis MCP server (kindtis/dumpanalysismcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DumpAnalysisMCP, 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.
12 DumpAnalysisMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.