get_metadata_keys · Obsidian Local REST API MCP Server MCP

WHAT IT DOES

What get_metadata_keys does on Obsidian Local REST API MCP Server

AI agents call get_metadata_keys to retrieve information from Obsidian Local REST API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why get_metadata_keys needs a policy

This tool only reads and retrieves metadata keys from existing notes. It does not create, modify, delete, execute code, or move money. While the server supports destructive operations (e.g., delete_item), this specific tool is purely informational and has no side effects on the vault.

From the tool's definition Tool retrieves 'all available frontmatter keys from notes' — a query operation that fetches metadata without modification. This is a GET-like operation on note metadata.

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

POLICY

How to control get_metadata_keys

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_metadata_keys": {}
  }
}

get_metadata_keys is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Obsidian Local REST API MCP Server tools

Destructive delete_item Delete a file or directory from the vault Write create_or_update_note Create or update a note with content and frontmatter. Performs upsert operation - creates Write write_file Write file content with different modes: overwrite (default), append, or prepend. Handles Read find_related_notes Find notes related to a given note based on shared tags, links, or backlinks Read get_daily_note Get daily note for a specific date. Handles common daily note naming conventions and file Read get_metadata_values Get all unique values for a specific frontmatter key Read get_note Get a specific note with its content and metadata (legacy) Read get_recent_notes Get recently modified notes, ordered by modification time

All 13 Obsidian Local REST API MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_metadata_keys

What does the get_metadata_keys tool do? +

Get all available frontmatter keys from notes. It is categorised as a Read tool in the Obsidian Local REST API MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_metadata_keys? +

Register the Obsidian Local REST API MCP Server MCP server in PolicyLayer and add a rule for get_metadata_keys: 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 Local REST API MCP Server. Nothing to install.

What risk level is get_metadata_keys? +

get_metadata_keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_metadata_keys? +

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

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

get_metadata_keys is provided by the Obsidian Local REST API MCP Server MCP server (j-shelfwood/obsidian-local-rest-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Obsidian Local REST API MCP Server tool call.

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

CHECK YOUR STACK →

Free to start. No card required.

13 Obsidian Local REST API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.