AI agents call obsidian_list_plugins to retrieve information from Obsidian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only retrieval of plugin metadata. It queries the state of plugins (installed/enabled) but does not modify, execute, or delete anything. The action is non-destructive and has no side effects—a typical 'list' operation mapping to the Read category.
From the tool's definition Tool name 'obsidian_list_plugins' and description 'Lists installed community + core plugins with enabled state' indicate a query operation that retrieves plugin information without modifying or executing anything.
Attacks that exploit this kind of access
Lists installed community + core plugins with enabled state. It is categorised as a Read tool in the Obsidian MCP Server, which means it retrieves data without modifying state.
Register the Obsidian MCP server in PolicyLayer and add a rule for obsidian_list_plugins: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Obsidian. Nothing to install.
obsidian_list_plugins is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the obsidian_list_plugins rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for obsidian_list_plugins. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
obsidian_list_plugins is provided by the Obsidian MCP server (yuchi-chang/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →