Create a new document in Frappe
AI agents use create_document to create or update resources in Frappe MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Frappe MCP Server environment.
The tool creates new documents in Frappe, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. However, severity is elevated to 'medium' because in the context of a Frappe ERP system, unrestricted document creation could be abused to insert malicious or fraudulent records (e.g., fake invoices, orders, or master data), potentially affecting business operations or…
From the tool's definition Tool name is 'create_document' and description states 'Create a new document in Frappe'. This is explicitly a document creation operation that modifies the database by adding new records.
Attacks that exploit this kind of access
Create a new document in Frappe. It is categorised as a Write tool in the Frappe MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Frappe MCP Server 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 Frappe MCP Server. 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 Frappe MCP Server MCP server (kiran-harbak/frappe_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 →