Plugins and Tool Approvals

Plugins and tool approvals

Plugins let LatchLoop connect agents to additional MCP tools, skills, and data sources. Install plugins from our marketplace or import private plugins and connect to custom MCP servers.

---

Plugin marketplace

The plugin marketplace is where you can discover and install available plugins.

Plugins may include:

• skills that teach agents how to use a system or workflow
• read-only tools for searching or fetching context
• write-capable tools that can create, update, or delete data
• authentication instructions or connection setup

Some plugins require authentication.

---

Private plugins

Private plugin imports are visible only to the owner or allowed scope. They are useful when your team wants to test a plugin before making it broadly available.

Admins can review, curate, and promote plugin manifests for public marketplace visibility.

---

Tool approvals in tasks

When an installed plugin tool requires approval, LatchLoop shows an approval card in the task AI sidebar. You have the ability to customize and override which tools require approval, both on a plugin basis and on a per-project basis.

The card includes:

• plugin name and branding
• tool name
• risk level
• whether the tool is read-only or write-capable
• arguments the agent wants to send
• task/project context
• Approve and Reject actions

The agent run pauses while waiting for your decision. If you approve, the run resumes and revalidates the request before executing the tool. If you reject or the request expires, the tool does not run.

---

Approval history

The Plugins page includes approval history for audit and recovery. Active approvals are easiest to handle from the task sidebar, where they are shown in context.

---

Troubleshooting

A plugin shows disconnected

• Confirm whether the plugin requires authentication.
• Reconnect or refresh the plugin connection if needed.
• For no-auth plugins, check whether tools have been discovered.

An approval card expired

• Ask the agent to retry the action if it is still needed.
• Review the new approval card before approving.

The run did not resume after approval

• Try approving again if the card still shows pending.
• If the card reports a resume error, reject or retry the task run.
• Contact support if approvals repeatedly fail to resume.