List all wikilinks in a vault that point to non-existent notes.
AI agents call find_broken_links to retrieve information from Vault Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a non-destructive information retrieval operation. It scans vault contents and reports broken link references but does not modify, delete, or execute anything. The operation has no side effects and produces no permanent changes to the vault. This aligns with the 'Read' category for tools that retrieve or query data.
From the tool's definition Tool description states 'List all wikilinks in a vault that point to non-existent notes.' The verb 'List' indicates a read operation that queries and retrieves data about broken links without modifying, deleting, or executing any actions.
Attacks that exploit this kind of access
List all wikilinks in a vault that point to non-existent notes. It is categorised as a Read tool in the Vault Memory MCP Server, which means it retrieves data without modifying state.
Register the Vault Memory MCP server in PolicyLayer and add a rule for find_broken_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 Vault Memory. Nothing to install.
find_broken_links 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 find_broken_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.
Set action: deny in the PolicyLayer policy for find_broken_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.
find_broken_links is provided by the Vault Memory MCP server (owrede/vault-memory). 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 →