get_linked_notes
Obtiene notas enlazadas mediante el grafo interno de Obsidian.
This record as markdown: /tools/a2rg-obsidian-mcp/get-linked-notes.md
What get_linked_notes does on Obsidian
AI agents call get_linked_notes to retrieve information from Obsidian without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Ruta relativa de la nota origen |
depth | number | — | Profundidad máxima: 1 a 3 |
limit | number | — | Límite opcional de resultados |
direction | string | — | Tipo de enlaces a recorrer |
Parameters from the server's own tool schema.
Why get_linked_notes is rated Low
Even though get_linked_notes only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs get_linked_notes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Obsidian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_linked_notes, this is the rule to start with:
get_linked_notes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Obsidian, apply this rule, and every get_linked_notes call is checked against it from then on.
Questions about get_linked_notes
Obtiene notas enlazadas mediante el grafo interno de Obsidian. It is categorised as a Read tool in the Obsidian MCP Server, which means it retrieves data without modifying state.
get_linked_notes accepts 4 parameters: path, depth, limit, direction. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Obsidian MCP server in PolicyLayer and add a rule for get_linked_notes: 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. Nothing to install.
get_linked_notes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_linked_notes 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.
Set action: deny in the PolicyLayer policy for get_linked_notes. 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.
get_linked_notes is provided by the Obsidian MCP server (@a2rg/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Obsidian, and thousands of servers like it.
This server
Across the catalogue