Add execute_code to MCP tools

[tigretigre]

Description

I have a setup where there are simultaneously MCP consumers that can modify the notebook and other consumers that can just query. I would like to run MCP with both the tools for querying and code-mode for modification, but the current setup has you choose one or the other. I would like to just make "code-mode" a tool amongst all the others, so that we can run both at the same time, and add a "mutates" attribute to each tool to indicate whether it should be permitted for read-only clients or not.

Are you willing to submit a PR? (You must receive approval from the team before submitting a PR.)

• Yes

Alternatives

No response

Additional context

No response

[Ram9199]

@tigretigre making code-mode a tool and adding a mutates attribute seems like the right direction.

I would consider treating mutates as one input to an approval/policy decision rather than only as a read-only-client filter. A useful future shape is:

• tool identity
• mutates / side-effect metadata
• client capability or trust level
• requested args/resource
• decision: allow, deny, approval_required
• audit record for what actually ran

That lets query-only clients filter safely now, while leaving room for approval-gated mutation later.