The Jenkins git tag action applies a tag to the git repository in the Jenkins workspace based on the git commit used in the build that is applying the tag. That type of action made sense when using centralized repositories that automatically applied the tag to the centralized repository. Applying a git tag in an agent workspace doesn't have many practical uses.

It mistakenly assumes that workspaces are persistent, when they are frequently ephemeral.

It mistakenly assumes that a tag in a workspace does not need to be pushed somewhere else for visibility.

It seems to require the workspace is on the Jenkins controller.

Do not add the git tag action unless the Jenkins administrator specifically enables it. Add a global configuration option to add the git tag action so that it does not use space in the left side links in the default use case.