obsidian_enable_plugin · Obsidian MCP: Risk & Policy

WHAT IT DOES

What obsidian_enable_plugin does on Obsidian

AI agents invoke obsidian_enable_plugin to trigger actions in Obsidian. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why obsidian_enable_plugin needs a policy

Enabling a plugin causes external code to run within the Obsidian instance. Community plugins can execute arbitrary code with full access to the filesystem and application, making this an Execute-category action with high severity — a malicious or compromised plugin could cause significant harm.

From the tool's definition Enables a community plugin by id

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

obsidian_enable_plugin Rate-limited

obsidian_enable_plugin stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "obsidian_enable_plugin": {
      "limits": [
        {
          "counter": "obsidian_enable_plugin_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Obsidian, so you can run agents against it safely.

FAQ

Questions about obsidian_enable_plugin

What does the obsidian_enable_plugin tool do? +

Enables a community plugin by id. It is categorised as a Execute tool in the Obsidian MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on obsidian_enable_plugin? +

Register the Obsidian MCP server in PolicyLayer and add a rule for obsidian_enable_plugin: 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.

What risk level is obsidian_enable_plugin? +

obsidian_enable_plugin is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit obsidian_enable_plugin? +

Yes. Add a rate_limit block to the obsidian_enable_plugin 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.

How do I block obsidian_enable_plugin completely? +

Set action: deny in the PolicyLayer policy for obsidian_enable_plugin. 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.

What MCP server provides obsidian_enable_plugin? +

obsidian_enable_plugin 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.