Add cpg_get_last_write MCP tool#2805
Open
narangtanmay wants to merge 2 commits into
Open
Conversation
|
Tanmay seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an MCP tool that returns the writes that may reach a given node's value, one-hop, control-flow-sensitive reaching definitions.
Node.reachingWrites()reads the node's existingprevDFGedges (already materialized byPointsToPass's kill/union analysis) and returns them asReachingWrite(source, granularity, functionSummary).cpg_get_last_writeexposes this over MCP: resolves a node by ID, runsreachingWrites(), returns the writing nodes with their dataflow granularity and whether the edge came from a function summary.This is deliberately different from
followPrevDFG: that API returns a single witness path by design (findAllPossiblePaths = false), so on a variable written on multiple branches before a merge it picks one arbitrary write.reachingWrites()returns all of them, the full "may" set.Test plan
No automated tests included yet, open question whether to add them before merge.
prevDFGsources come back./gradlew :cpg-core:compileKotlin :cpg-mcp:compileKotlinclean