Count records of a doctype matching optional filters.
AI agents call frappe_count to retrieve information from Frappe MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation to count records matching specified criteria. It has no side effects, cannot modify, delete, or execute code, and simply returns a count metric. The read-only nature of the server and the pattern of sibling tools confirm this classification. Severity is low because misuse would only result in database queries without risk to data integrity or system stability.
From the tool's definition Tool description states 'Count records of a doctype matching optional filters.' The verb 'count' is a read-only operation that retrieves aggregate information without modifying data.
Attacks that exploit this kind of access
Count records of a doctype matching optional filters. It is categorised as a Read tool in the Frappe MCP MCP Server, which means it retrieves data without modifying state.
Register the Frappe MCP server in PolicyLayer and add a rule for frappe_count: 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. Nothing to install.
frappe_count 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 frappe_count 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 frappe_count. 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.
frappe_count is provided by the Frappe MCP server (tourscale-repos/frappe-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 →