answer_question
AI agents call answer_question 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 appears designed to retrieve and process information from the Graph-RAG system to answer user queries. This is a Read operation as it queries existing data without modifying, executing external commands, or causing irreversible changes. The confidence is moderate (0.75) rather than high because the description is empty, requiring inference from the tool name and server context.
From the tool's definition Tool name 'answer_question' combined with server context describing 'intelligent Q&A over your Obsidian vault' indicates a query/retrieval operation.
Attacks that exploit this kind of access
answer_question. 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 answer_question: 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.
answer_question 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 answer_question 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 answer_question. 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.
answer_question 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 →