Low Risk

get_outgoing_links

MCP Tool: Finds all outgoing Obsidian links [[...]] in a note.

How to control get_outgoing_links ↓

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

Low Risk

This is a pure information retrieval operation that scans note content for link references and returns that data. It has no capability to modify, delete, execute code, or create side effects. The blast radius of misuse is minimal—an agent could only learn about note relationships, which presents no security or data integrity risk.

From the tool's definition The tool 'finds all outgoing Obsidian links [[...]] in a note' — it retrieves and queries link metadata from existing notes with no modification, deletion, or side effects.

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

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

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

get_outgoing_links 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 Tool 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.

Go deeper

What does the get_outgoing_links tool do? +

MCP Tool: Finds all outgoing Obsidian links [[...]] in a note. It is categorised as a Read tool in the Obsidian MCP Tool Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_outgoing_links? +

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

What risk level is get_outgoing_links? +

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

Can I rate-limit get_outgoing_links? +

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

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

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

Deterministic rules across all 18 Obsidian MCP Tool Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

18 Obsidian MCP Tool Server tools catalogued and risk-classified — across an index of 42,500+ 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.