bases_upsert_rows

THE RISK

Medium Risk

Why bases_upsert_rows needs a policy

This tool creates or modifies note frontmatter data through upsert operations. While the changes are reversible (not destructive), the tool modifies structured data in Obsidian notes.

From the tool's definition Tool performs 'set operations for notes' and 'upsert' (create or update) via frontmatter manipulation, which modifies note metadata reversibly.

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

POLICY

How to control bases_upsert_rows

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 bases_upsert_rows:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bases_upsert_rows": {
      "limits": [
        {
          "counter": "bases_upsert_rows_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

bases_upsert_rows stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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.

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_search_replace Headless-guarded filesystem exact search/replace for filePath targets. 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 obsidian_manage_canvas Headless filesystem JSON Canvas helper. Validates, creates, adds text nodes, and connects

All 15 Optimike Obsidian MCP tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about bases_upsert_rows

What does the bases_upsert_rows tool do? +

Headless-guarded filesystem frontmatter set operations for notes referenced by a .base. Unset is not supported. It is categorised as a Write tool in the Optimike Obsidian MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on bases_upsert_rows? +

Register the Optimike Obsidian MCP server in PolicyLayer and add a rule for bases_upsert_rows: 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 bases_upsert_rows? +

bases_upsert_rows is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit bases_upsert_rows? +

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

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

bases_upsert_rows 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 →