List GL Entry records (ERPNext general ledger). Filter by account, party (customer/supplier), date range.
AI agents call erpnext_gl_entries 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 retrieves and queries general ledger entries from an ERP system without performing any write, destructive, execute, or financial operations. It is a straightforward read operation that returns existing data. The read-only nature of the server and the query-only semantics of the tool confirm this classification.
From the tool's definition Tool description explicitly states 'List GL Entry records' with filtering capabilities (account, party, date range). Server is described as 'Read-only MCP server' enabling agents to 'query' data.
Attacks that exploit this kind of access
List GL Entry records (ERPNext general ledger). Filter by account, party (customer/supplier), date range. 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 erpnext_gl_entries: 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.
erpnext_gl_entries 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 erpnext_gl_entries 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 erpnext_gl_entries. 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.
erpnext_gl_entries 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 →