obsidian_search_replace

THE RISK

High Risk

Why obsidian_search_replace needs a policy

This tool performs search and replace operations directly on the filesystem across file path targets. While it modifies file content (Write), the ability to execute arbitrary search/replace across filesystem paths with potentially broad scope elevates this to Execute-level risk. It could overwrite critical content in many files if misused, and the 'headless-guarded' qualifier suggests it operates at a system level.

From the tool's definition "exact search/replace for filePath targets" with "Headless-guarded filesystem" access

Documented attack patterns abuse exactly the kind of access obsidian_search_replace gives an agent:

POLICY

How to control obsidian_search_replace

PolicyLayer is an MCP gateway — it sits between your AI agents and Optimike Obsidian MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for obsidian_search_replace:

policy.json

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

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

Create a free account and register Optimike Obsidian MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Optimike Obsidian MCP tools

Destructive obsidian_admin_filesystem Headless-filesystem admin batch operations with dry-run by default. Supports sandbox-safe Destructive obsidian_delete_note Headless-guarded filesystem delete for explicit filePath targets. Requires expectedHash or Execute obsidian_runtime_maintenance Runs integrity checks, maintenance, or cache refresh actions for the local shared runtime. Write obsidian_batch_frontmatter Headless-filesystem batch frontmatter set with dry-run support. Protected keys remain bloc Write bases_create Headless-guarded filesystem .base create/validate. Writes YAML directly and does not evalu Write bases_upsert_config Headless-guarded filesystem .base config replacement/validation. Write bases_upsert_rows Headless-guarded filesystem frontmatter set operations for notes referenced by a .base. Un Write obsidian_manage_canvas Headless filesystem JSON Canvas helper. Validates, creates, adds text nodes, and connects

All 15 Optimike Obsidian MCP tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Optimike Obsidian MCP → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about obsidian_search_replace

What does the obsidian_search_replace tool do? +

Headless-guarded filesystem exact search/replace for filePath targets. It is categorised as a Execute tool in the Optimike Obsidian MCP 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_search_replace? +

Register the Optimike Obsidian MCP server in PolicyLayer and add a rule for obsidian_search_replace: 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 Optimike Obsidian MCP. Nothing to install.

What risk level is obsidian_search_replace? +

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

Can I rate-limit obsidian_search_replace? +

Yes. Add a rate_limit block to the obsidian_search_replace 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_search_replace completely? +

Set action: deny in the PolicyLayer policy for obsidian_search_replace. 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_search_replace? +

obsidian_search_replace is provided by the Optimike Obsidian MCP server (optimikelabs/optimike-obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Optimike Obsidian MCP tool call.

Start from Optimike Obsidian MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →