Which Tools Ask Before Acting, Spelled Out
What changed: A documentation-only release. The README’s safety section now lists every tool that stops for a human confirmation, and explains the rule behind the list, so you can tell at a glance what the agent will do on its own and what it will always ask about first. The stale pre-release note that said the package was not on npm yet is gone.
Where to find it: The package README, on the npm page for @nimbio/mcp-server and in the repository.
What you’ll see: Seven tools ask first: opening a gate, holding one open indefinitely, revoking a guest link, removing a home, replaying webhook deliveries, messaging every member, and switching access-code mode. Everything else that deletes something you can re-create, such as a hold-open window or a webhook, is flagged as destructive in the tool listing but runs without a prompt, because a follow-up call can undo it.
What you need to do: No action needed. npx -y @nimbio/mcp-server picks up the new version automatically; nothing about the tools or configuration changed.
Who this affects: Community Managers and developers running the MCP server.