Get document with full context including links, references, and AI metadata
AI agents call get_document_context to retrieve information from Helios-9 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 and queries document information (context, links, references, metadata) without creating, modifying, deleting, or executing anything. It is purely informational with no blast radius for misuse beyond potential data disclosure, which is inherent to read-only operations.
From the tool's definition Tool name 'get_document' and description states it 'Get[s] document with full context including links, references, and AI metadata' — retrieves document data with no modification or side effects mentioned.
Attacks that exploit this kind of access
Get document with full context including links, references, and AI metadata. It is categorised as a Read tool in the Helios-9 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Helios-9 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 Helios-9 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 Helios-9 MCP Server MCP server (jakedx6/helios9-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 →