AI agents use restore_document to create or update resources in Oblio — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Oblio environment.
This tool modifies document state by changing a cancelled document back to active/valid status. While it reverses a prior cancellation (rather than destructively deleting), it still constitutes irreversible state change in a financial/accounting context where document status directly impacts tax records and legal compliance. The restoration could affect invoice validity, payment flows, and regulatory submissions.
From the tool's definition Tool restores a previously cancelled document via PUT /api/docs/{type}/restore. PUT methods modify state; restoration reverses a cancellation, which is a write operation that changes document status.
Attacks that exploit this kind of access
Restores a previously cancelled document in Oblio via PUT /api/docs/{type}/restore. It is categorised as a Write tool in the Oblio MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Oblio MCP server in PolicyLayer and add a rule for restore_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.
restore_document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the restore_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 restore_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.
restore_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.
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 →