get_file_contents

THE RISK

Low Risk

Why get_file_contents needs a policy

This tool retrieves and returns file contents without modifying, deleting, or executing anything. It is a simple read operation with no side effects, making it categorically Read and of low severity since an agent can only access existing vault data without causing harm.

From the tool's definition Tool name 'get_file_contents' and description 'Return the content of a single file in your vault' indicate data retrieval with no modification or deletion.

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

POLICY

How to control get_file_contents

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

policy.json

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

get_file_contents 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 MCP server for Obsidian — 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 MCP server for Obsidian tools

Destructive delete_file Delete a file or directory from your vault. Write append_content Append content to a new or existing file in the vault. Write patch_content Insert content into an existing note relative to a heading, block reference, or frontmatte Read list_files_in_dir Lists all files and directories in a specific Obsidian directory Read list_files_in_vault Lists all files and directories in the root directory of your Obsidian vault Read search Search for documents matching a specified text query across all files in the vault

All 7 MCP server for Obsidian 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_file_contents

What does the get_file_contents tool do? +

Return the content of a single file in your vault. It is categorised as a Read tool in the MCP server for Obsidian MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_file_contents? +

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

What risk level is get_file_contents? +

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

Can I rate-limit get_file_contents? +

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

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

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

Enforce policy on every MCP server for Obsidian tool call.

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

CHECK YOUR STACK →