get_outgoing_links_tool
AI agents call get_outgoing_links_tool 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.
This tool retrieves outgoing links from notes, which is a query/retrieval operation with no side effects. It fits the Read category pattern of examining data relationships. The tool description is empty, which slightly reduces confidence, but the naming convention and sibling tool context strongly indicate this is a non-destructive read operation that traverses note link structures in the Obsidian vault.
From the tool's definition Tool name 'get_outgoing_links_tool' indicates retrieval of link information. The server description explicitly mentions 'link management' as a supported capability, and the sibling tools include 'get_backlinks_tool' and 'find_broken_links_tool', which are…
Attacks that exploit this kind of access
get_outgoing_links_tool. It is categorised as a Read tool in the Obsidian MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for get_outgoing_links_tool: 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.
get_outgoing_links_tool 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_outgoing_links_tool 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_outgoing_links_tool. 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_outgoing_links_tool is provided by the Obsidian MCP Server MCP server (suhailnajeeb/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →