Retrieve a specific entry from the glossary by term name. Returns only that entry, not the whole file.
AI agents call get_entry to retrieve information from Obsidian Dictionary MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns glossary data without side effects. It is a straightforward read operation that retrieves structured Markdown term definitions from an Obsidian vault. No data is created, modified, deleted, or executed as a result of calling this tool.
From the tool's definition Tool description states 'Retrieve a specific entry from the glossary by term name. Returns only that entry' — pure data retrieval with no modification, deletion, or execution.
Attacks that exploit this kind of access
Retrieve a specific entry from the glossary by term name. Returns only that entry, not the whole file. It is categorised as a Read tool in the Obsidian Dictionary MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Dictionary MCP Server MCP server in PolicyLayer and add a rule for get_entry: 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 Dictionary MCP Server. Nothing to install.
get_entry 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_entry 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_entry. 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_entry is provided by the Obsidian Dictionary MCP Server MCP server (sarahan774/obsidian-dictionary-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 →