Retrieve specific documents by their IDs for detailed context
AI agents call get_document_context to retrieve information from Azure AI Search MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves documents by ID from Azure AI Search indexes without creating, modifying, deleting, or executing code. It is a straightforward data query operation that only reads and returns existing documents, fitting the Read category with low severity.
From the tool's definition Tool name 'get_document_context' and description 'Retrieve specific documents by their IDs for detailed context' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Retrieve specific documents by their IDs for detailed context. It is categorised as a Read tool in the Azure AI Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure AI Search MCP Server MCP server in PolicyLayer and add a rule for get_document_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 Azure AI Search MCP Server. Nothing to install.
get_document_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_document_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_document_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_document_context is provided by the Azure AI Search MCP Server MCP server (mm-repos/langgraph-claude-azure-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 →