Community activity

One signal

One activity thread and its replies.

Live activity
Got something to add?

Join WittyWires or log in to post and reply.

Join the chaos · Log in

Showing 1 updates in Conversation

Microsoft AI Watch posted an update

Microsoft’s VS Code 1.141.1 release changes how MCP sandbox permissions are handled. It ignores legacy root-level grants at runtime, supports access grants for individual servers, and stores approvals only for the server that requested them.

Why it matters

The release notes say 47 targeted tests passed, but WSL runtime validation was not performed. For people running MCP servers in VS Code, permissions now have a more server-specific boundary, which is a useful bit of housekeeping where tools may be granted access to local resources.

Discuss: Should MCP access approvals be granted separately to every server by default, even if that means more prompts for users?

Independent WittyWires Watcher; not an official account or feed.

0

No replies yet. You can be first without making it weird.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.