Plugin security and trust - Claude Code Docs
Documentation Index Fetch the complete documentation index at: /docs/llms.txt Use this file to discover all available pages before exploring further. Skip to main content Assistant Responses are generated using AI and may contain mistakes. A Claude Code plugin you install can execute arbitrary code on your machine with your user privileges. You install a plugin from a marketplace, which is the catalog Claude Code fetches it from.
Some marketplace names are reserved for Anthropic’s own marketplaces , and every other marketplace is third-party. A marketplace’s name tells you who publishes the catalog, not what each plugin in it does, so review a plugin before you install it whichever marketplace it comes from. Read this page if you’re deciding whether to install a plugin, or if you review tools before your team can use them. These cases are covered on other pages: Claude Code’s own security model : see Security Restricting or requiring plugins for an organization : see Manage plugins for your organization The security-guidance or claude-security plugins : this page isn’t about them.
See security-guidance and claude-security Start with what a plugin can do and which marketplaces are Anthropic’s , then review the plugin before you install it . Understand what a plugin can do A plugin can carry content that runs code on your machine with your user privileges and content that enters Claude’s context as instructions, so review a plugin before you install it . Here’s what an installed plugin can do: Hooks : a plugin’s hooks run as shell commands at points in Claude Code’s lifecycle, such as before or after a tool call.
Monitors : a plugin’s monitors run as background shell commands that Claude Code starts on its own when the session starts, when you reload plugins, or the first time a named skill runs. Mods : a plugin’s mod runs JavaScript inside Claude Code with your permissions. To list what a mod does before you install it, see Decide whether to trust a mod . MCP and LSP servers : Claude Code connects to the MCP servers an enabled plugin declares and gives Claude their tools.
A stdio MCP server runs as a process that Claude Code starts on your machine. Claude Code also starts the language servers the plugin declares. bin/ directory : Claude Code adds each enabled plugin’s bin/ directory to the PATH of the Bash tool’s shell, so Claude’s Bash commands can run any executable there. A command that Claude runs with the PowerShell tool gets those directories on its PATH when it runs outside the sandbox , and not when it runs inside it.
Skills, commands, and agents : these enter Claude’s context as instructions, so they influence what Claude does with the tools it already has. Updates : when auto-update is on for the marketplace you installed a plugin from, Claude Code updates that plugin in the background, so the files you reviewed can change on disk. When auto-update runs has the timing. To turn auto-update on or off per marketplace, see Keep plugins updated .
Claude Code’s permission rules and sandbox cover the tool calls Claude makes, not the code a plugin runs by itself: Hooks, monitors, and server processes : command hooks and monitors are shell commands that run with your full user permissions. Claude Code runs hooks, monitors, MCP servers, LSP servers, and the processes a mod starts outside the sandbox. Claude’s tool calls : a call to one of the plugin’s MCP tools, and a Bash command that runs an executable from the plugin’s bin/ , are tool calls, so your permission rules apply to them.
For what a mod can do to a tool call, see Decide whether to trust a mod . Installing a plugin also enables it, unless its manifest or marketplace entry sets defaultEnabled: false and you haven’t enabled it yourself. To remove a plugin you no longer trust, see Remove a plugin you no longer trust . Identify Anthropic’s marketplaces by name A marketplace’s name places it in one of three tiers: official, community, or third-party.
Claude Code accepts the official and community names only for marketplaces sourced from github.com/anthropics/ repositories, so a third-party marketplace can’t present itself as an Anthropic one. A marketplace that a coworker or your organization publishes is third-party. The table lists which names fall in each tier: Tier Which marketplaces Official The official marketplace names , such as claude-plugins-official Community claude-community , claude-plugins-community , and healthcare Third-party Every other marketplace Where the claude-community catalog pins a plugin to a commit SHA, which it does for nearly every entry, Claude Code refuses to install a different commit.
Official marketplace names These marketplace names make up the official tier: claude-plugins-official claude-code-marketplace claude-code-plugins anthropic-marketplace anthropic-plugins agent-skills anthropic-agent-skills life-sciences knowledge-work-plugins claude-for-legal claude-for-financial-services financial-services-plugins first-party-plugins claude-tag-plugins For how the official and community marketplaces differ and where to browse what each one lists, see Anthropic’s marketplaces .
Review a plugin before you install Before you install a plugin, look at what it adds and where it comes from. 1 Check the marketplace's source In your shell, run claude plugin marketplace list to print the source each marketplace was added from, such as a GitHub repository or a directory. 2 Read the details pane In a Claude Code session, run /plugin and select the plugin. The details pane shows a Will install section listing the plugin’s commands, agents, skills, hooks, and MCP and LSP servers.
For a plugin Anthropic has no published component data for, the section shows what the marketplace entry declares, or a note: Components will be discovered at installation for a plugin stored inside the marketplace, or Component summary not available for remote plugin for one fetched from elsewhere. 3 Read the plugin's source In the details pane, select Open homepage or View on GitHub below the install options. If the pane offers neither, open the marketplace repository you found in the first step.
Find the plugin’s directory there. The Will install section shows that a hook exists but not what it runs, so read these files in the plugin’s directory: hooks/hooks.json : the command each hook runs .mcp.json : each server’s command or URL bin/ : every file in the directory 4 List what the plugin contains Clone the repository that holds the plugin’s directory, then run claude --plugin-dir <plugin directory> plugin details <plugin name> in your shell to see what Claude Code finds in it.
The command reads the plugin’s files without starting a session and prints a Component inventory listing the plugin’s skills and commands, agents, hooks with each hook’s event, and MCP and LSP servers. After you install a plugin, run claude plugin details <plugin name> in your shell to print the same Component inventory for the installed copy under ~/.claude/plugins/cache/<marketplace>/<plugin>/<version>/ . Remove a plugin you no longer trust In your shell, run claude plugin uninstall <plugin> with the --scope you installed it at.
Then check what the uninstall removed and what it left: Persistent data : by default, when that was the last scope the plugin was installed at, uninstalling also deletes the plugin’s persistent data directory. For --keep-data and the other cases where it stays, see plugin uninstall . Cached files : the plugin’s files stay on disk under ~/.claude/plugins/cache/ for 14 days before a background sweep removes them . After you uninstall your last plugin, orphaned directories stay until you install another.
To delete the files now, remove the plugin’s directory under ~/.claude/plugins/cache/<marketplace>/<plugin>/ yourself. The marketplace : if you don’t trust the marketplace’s owner either, remove the marketplace too, which unin
The rest of this page is on the live site.