Get a count of documents matching filters
AI agents call get_document_count 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 retrieves a count of documents based on filter criteria, which is a non-destructive read operation. It has no side effects—it only queries and returns numeric data. No data is created, modified, deleted, or executed. The low severity reflects minimal blast radius if misused by an AI agent, as the worst case would be information disclosure or resource exhaustion through repeated queries.
From the tool's definition Tool name 'get_document_count' and description 'Get a count of documents matching filters' indicate a read-only query operation that retrieves aggregated metadata without modifying data.
Attacks that exploit this kind of access
Get a count of documents matching filters. 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 get_document_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 Server. Nothing to install.
get_document_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 get_document_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 get_document_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.
get_document_count 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 →