Perform semantic search using query text to find relevant notes in your Obsidian vault
AI agents call lookup to retrieve information from Ob Smart Connections without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries an Obsidian vault using semantic search to locate and retrieve notes based on text input. It has no side effects, does not modify data, execute code, or commit financial transactions. The query returns results without altering the vault.
From the tool's definition Tool description states 'Perform semantic search using query text to find relevant notes' — a retrieval operation with no modification or deletion capability.
Documented attack patterns abuse exactly the kind of access lookup gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ob Smart Connections, and nothing reaches the server without passing your rules. This is the rule we recommend for lookup:
{
"version": "1",
"default": "deny",
"tools": {
"lookup": {}
}
}lookup is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Perform semantic search using query text to find relevant notes in your Obsidian vault. It is categorised as a Read tool in the Ob Smart Connections MCP Server, which means it retrieves data without modifying state.
Register the Ob Smart Connections MCP server in PolicyLayer and add a rule for lookup: 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 Ob Smart Connections. Nothing to install.
lookup 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 lookup 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 lookup. 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.
lookup is provided by the Ob Smart Connections MCP server (yejianye/ob-smart-connections-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ob Smart Connections, 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.
4 Ob Smart Connections tools catalogued and risk-classified — across an index of 43,000+ MCP servers.