Low Risk

get_property_values

List all values for a property

How to control get_property_values ↓

What get_property_values does on Obsidian MCP Server

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

Low Risk

Why get_property_values needs a policy

This tool reads and retrieves property values from the Obsidian vault, which is a data retrieval operation with no side effects. However, in the context of an Obsidian vault containing personal notes, task lists, and knowledge bases, the data retrieved could be sensitive (e.g., property values used in metadata across notes).

From the tool's definition Tool name 'get_property_values' and description 'List all values for a property' indicate a retrieval/query operation that returns data without modification.

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

How to control get_property_values

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_property_values": {}
  }
}

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

  1. Create a free account and register Obsidian MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_property_values

What does the get_property_values tool do? +

List all values for a property. It is categorised as a Read tool in the Obsidian MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_property_values? +

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

What risk level is get_property_values? +

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

Can I rate-limit get_property_values? +

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

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

get_property_values is provided by the Obsidian MCP Server MCP server (kynlos/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 Obsidian MCP Server tool call.

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

Free to start. No card required.

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.