Find DocTypes in the system matching a search term
AI agents call find_doctypes 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.
find_doctypes performs a read-only search operation to discover and list DocTypes matching criteria. It has no side effects, does not create, modify, or delete data, and does not execute arbitrary code or trigger external operations. This is a typical query/discovery tool that falls squarely into the Read category with low severity since misuse would only expose schema information, not cause operational damage.
From the tool's definition Tool description states 'Find DocTypes in the system matching a search term' — this is a search/query operation that retrieves metadata about available document types without modifying any data.
Attacks that exploit this kind of access
Find DocTypes in the system matching a search term. 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 find_doctypes: 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.
find_doctypes 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 find_doctypes 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 find_doctypes. 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.
find_doctypes 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 →