WPFVisualTreeMcp

The project primarily operates in a 'self-hosted' mode where the target WPF application explicitly includes and initializes the inspector DLL, implying consent. The `WpfVisualTreeMcp.Injector` component, which would handle DLL injection into arbitrary external processes, is explicitly stated as a 'stub implementation' and not yet functional for complex managed code injection. Inter-process communication uses Named Pipes with specified ACLs for local, secure interaction. No 'eval' or obfuscation is noted. While the *concept* of injecting into other processes inherently carries risks, its current implementation and recommended usage mitigate immediate security concerns.