AI agents use create_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.
The tool creates financial documents (invoices, proformas, delivery notices) in an accounting system, which qualifies as Write (creates/modifies data reversibly). It is not Financial because no money changes hands directly; it is not Execute because the operation is deterministic and documented.
From the tool's definition Creates an invoice (factura), proforma, or delivery notice (aviz) in Oblio via POST /api/docs/{type}—this is a create operation that modifies financial records.
Attacks that exploit this kind of access
Creates an invoice (factura), proforma, or delivery notice (aviz) in Oblio via POST /api/docs/{type}. 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 create_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.
create_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 create_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 create_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.
create_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 →