Check if a document exists
AI agents call check_document_exists to retrieve information from Frappe MCP Server 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 existence check against Frappe documents, which is a read-only operation with no side effects. It queries state without creating, modifying, or deleting data. The low severity reflects minimal blast radius if misused by an AI agent—at worst, it returns boolean information about document presence.
From the tool's definition Tool name 'check_document_exists' and description 'Check if a document exists' indicate a query operation that retrieves existence status without modification.
Attacks that exploit this kind of access
Check if a document exists. It is categorised as a Read tool in the Frappe MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Frappe MCP Server MCP server in PolicyLayer and add a rule for check_document_exists: 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.
check_document_exists 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 check_document_exists 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 check_document_exists. 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.
check_document_exists 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 →