feat(security): wire capabilityPolicy across execution surfaces (#690) - #745
Conversation
… loop Pass the loaded capability policy into configured command execution across product, tool adapters, loop, and MCP surfaces, and document that MCP confirmations are operation-scoped. Refs #690. Co-authored-by: Cursor <cursoragent@cursor.com>
CodeDecay PR CheckLead catch: No direct high-signal catch found CodeDecay did not find a strong direct regression or weak-test signal in this run. Risk: Medium · Merge 39/100 · Decay 43/100 · Security 0/100 This score is conservative pending stronger direct evidence. Treat structural-only signals as review guidance, not proof of a regression. Full CodeDecay reportCodeDecay ReportOverall risk: Medium
Changed Files
Likely Impacted Areas
Normalized Impact GraphGraph artifact:
Symbol Impact EvidenceGraph artifact:
Language And Parser Coverage
Merge Risk Breakdown
Top contributors:
Dampeners:
Notes:
Decay Risk Breakdown
Top contributors:
Dampeners:
Notes:
Security Risk Breakdown
Security Matcher Coverage
Test Evidence
Changed Path Test Proof
Untrusted Memory Context
High Risk Findings
Medium Risk Findings
Low Risk Findings
Recommended Checks
NotesCodeDecay is deterministic and local-first. This report was generated without telemetry, API keys, LLMs, or model calls. Found by CodeDecay - deterministic, local-first, no telemetry. |
Summary
createSafeCommandPolicyand threadssafety.capabilityPolicythrough CLI product/loop, command adapters, and OSS tool adapters.Test plan
tsc -p tsconfig.base.json --noEmitvitest run packages/execution/test packages/adapters/test packages/tool-adapters/test packages/mcp/test/mcp-execution-tools.test.tsRefs #690 (does not close; remaining: sandbox isolation, full adversarial UAT corpus, session-scoped approval expiry).