Help Center
All articlesConnectors And MCP

Review connector health

Use connector status, tool registration, and diagnostics to keep agent tools reliable.

Updated June 19, 20264 min read

Connector health is operational risk

A stale token, broken MCP server, or unexpected tool schema can make an agent fail or act differently than expected. Review connector health before relying on a tool for production workflows.

Iron Gorilla connectors page with MCP servers, native integrations, status, and tool counts.
Connectors show each tool surface with owner, health, scope, and registered capabilities.

What healthy looks like

A healthy connector is connected, recently checked, and owned by the team that understands the system behind it. Tool counts and permissions should match what agents are expected to use, and unexpected changes should be investigated as blocked actions or operational risk.

Diagnostic messages should be quiet, recent, and understandable. Before changing or removing a connector, make sure the agents that depend on it are known.

Connectors And MCPAdd a connector or MCP server

Register tools that agents can use while preserving ownership and scoped access.

Operations Command CenterInvestigate blocked actions

Review why an action was stopped and decide whether policy, access, or agent behavior should change.

Operations Command CenterReview pending approvals

Decide held actions with the agent, policy, trust, and evidence in view.

Need help?

Tell us where you got stuck.

Share what you were trying to do, what happened, and how urgent it is. We will route it to the right team.

Submit a ticket