Bridgecore

Labels

What happens if this step was wrong?

Before anything runs, every step in a Bridgecore plan says whether it can be taken back. The label comes from the tool itself (its operation, HTTP method or MCP annotation), so the same tool always gets the same label — it never depends on how you phrased the need.

LabelMeaningCapabilities (3,597)Examples
read-only
only reads
changes nothing1,485github.file.get, github.file.list, github.issue.get, github.organization.getRepositories, github.organization.getMembers, github.pullRequest.get
reversible
can be undone
can be undone by hand1,363github.file.create, github.file.edit, github.issue.create, github.issue.edit, github.issue.lock, github.pullRequest.create
irreversible
can’t be undone
out in the world once it runs — say “and ask me first” to put an Approve / Decline button before it749github.file.delete, github.issue.createComment, github.pullRequest.close, github.pullRequest.createComment, github.pullRequest.editComment, github.release.delete

How it is computed

In the 67 recipe steps on this site

🟢 read-only 27 · 🟡 reversible 18 · 🔴 irreversible 22. The label is also written into every node’s notes in the n8n file (reversibility: …) and returned by the MCP tools plan_automation, find_recipe, make_n8n_workflow and do.