Wymcp tool scripts — the scripts this node has accepted, and running one.

A thin boundary over YmerNode.Scripts, wiring only the framework's callbacks. What a script is, what acceptance means, and why a run is bounded and killed rather than waited on live in the context's own moduledoc and in YmerNode.Scripts.Runner's.

Destructive and open-world, which no other tool on this node is. A script reaches the network with the node's own permissions, so run is the one call here whose effects can land outside this machine and outside this node's control — and the node cannot tell, in advance, which script will. Both hints are properties of the tool, not of the average call.

Authoring lives next door in YmerNode.Mcp.Tools.ScriptAuthor. The split is the point: a client can be granted the ability to run what has been accepted without being granted the ability to accept anything.