Get source context around a specific line in a file
AI agents call get_source_context to retrieve information from Mcp Debugger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays source code context without creating, modifying, executing, or deleting any data. It is purely informational for debugging purposes, making it a Read category tool with low severity since source code exposure during a debugging session is a typical and low-risk operation.
From the tool's definition Tool name 'get_source_context' and description 'Get source context around a specific line in a file' indicate read-only retrieval of source code content with no modification or execution capabilities.
Attacks that exploit this kind of access
Get source context around a specific line in a file. It is categorised as a Read tool in the Mcp Debugger MCP Server, which means it retrieves data without modifying state.
Register the Mcp Debugger 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 Mcp Debugger. 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 Mcp Debugger MCP server (@debugmcp/mcp-debugger). 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 →