Get surrounding context for a specific chunk.
AI agents call explore_chunk_context to retrieve information from Graph Rag Obsidian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves contextual information about a chunk from the knowledge base. It has no side effects, does not modify data, does not execute code, and does not delete or move resources. This is a classic Read operation with minimal blast radius if misused by an agent—the worst case being that the agent retrieves irrelevant or sensitive context it shouldn't see, but no data is altered or destroyed.
From the tool's definition Tool name is 'explore_chunk_context' and description states it will 'Get surrounding context for a specific chunk.' This is a query/retrieval operation with no modification, deletion, or code execution.
Attacks that exploit this kind of access
Get surrounding context for a specific chunk. It is categorised as a Read tool in the Graph Rag Obsidian MCP Server, which means it retrieves data without modifying state.
Register the Graph Rag Obsidian MCP server in PolicyLayer and add a rule for explore_chunk_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 Graph Rag Obsidian. Nothing to install.
explore_chunk_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 explore_chunk_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 explore_chunk_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.
explore_chunk_context is provided by the Graph Rag Obsidian MCP server (nickshffer/graph-rag-mcp-server). 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 →