AI agents call get_document to retrieve information from Oblio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple GET request to fetch an existing document. It retrieves data without creating, modifying, deleting, or executing any operations. The GET HTTP method and 'retrieves' language confirm this is a read operation with minimal risk unless the retrieved documents contain highly sensitive financial data, but the action itself is non-destructive and reversible.
From the tool's definition Tool name 'get_document' and description 'Retrieves a single document from Oblio via GET /api/docs/{type}' indicate a read-only retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
Retrieves a single document from Oblio via GET /api/docs/{type}. It is categorised as a Read tool in the Oblio MCP Server, which means it retrieves data without modifying state.
Register the Oblio MCP server in PolicyLayer and add a rule for get_document: 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 Oblio. Nothing to install.
get_document 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 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. 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 is provided by the Oblio MCP server (valentinludu/oblio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_document is one line of Oblio's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →