get_entity_context
Get rich context for a specific entity including relationships
This record as markdown: /tools/aegntic-aegntic-mcp/get-entity-context.md
What get_entity_context does on Obsidian Elite RAG MCP Server
AI agents call get_entity_context to retrieve information from Obsidian Elite RAG MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_entity_context is rated Low
This tool retrieves and queries contextual information about entities and their relationships within the Obsidian vault's knowledge graph. It performs a read-only operation with no side effects, no code execution, no data modification, and no irreversible actions. The severity is low because retrieval of existing context poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_entity_context' and description 'Get rich context for a specific entity including relationships' indicate retrieval of context and relationship data from the knowledge graph without modification.
Attacks that exploit this kind of access
The rule that runs get_entity_context safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Obsidian Elite RAG MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_entity_context, this is the rule to start with:
get_entity_context is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Obsidian Elite RAG MCP Server, apply this rule, and every get_entity_context call is checked against it from then on.
Questions about get_entity_context
Get rich context for a specific entity including relationships. It is categorised as a Read tool in the Obsidian Elite RAG MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Elite RAG MCP Server MCP server in PolicyLayer and add a rule for get_entity_context: 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 Elite RAG MCP Server. Nothing to install.
get_entity_context 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_entity_context 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_entity_context. 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_entity_context is provided by the Obsidian Elite RAG MCP Server MCP server (aegntic/aegntic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Obsidian Elite RAG MCP Server, and thousands of servers like it.
This server
Across the catalogue