get_note_info_tool
AI agents call get_note_info_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.
The 'get_' prefix strongly suggests a read-only retrieval operation that fetches metadata or content from an Obsidian note without modifying it. No side effects are implied. Despite the empty description lowering confidence slightly, the tool name and server context provide sufficient evidence of a Read classification. Severity is low as retrieving note information poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_note_info_tool' with 'get' prefix indicates data retrieval. Description is empty, but context from sibling tools (create_note, delete_note, edit_note_section, etc.) and server description mentioning 'note management' and 'search' establish this…
Attacks that exploit this kind of access
get_note_info_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_note_info_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_note_info_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_note_info_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_note_info_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_note_info_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 →