frappe_list_reports

// WHEN AI AGENTS USE THIS TOOL

AI agents call frappe_list_reports to retrieve information from Frappe Dev MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON FRAPPE_LIST_REPORTS

Even though frappe_list_reports only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

frappe-dev-mcp-server.yaml

tools:
  frappe_list_reports:
    rules:
      - action: allow

See the full Frappe Dev MCP Server policy for all 29 tools.

// DETAILS

Tool Name frappe_list_reports

Category Read

MCP Server Frappe Dev MCP Server MCP Server

Risk Level Low

// MORE FRAPPE DEV MCP SERVER TOOLS

Destructive frappe_delete_document Execute frappe_call_method Execute frappe_run_bench_command Execute frappe_run_doctype_report Execute frappe_run_query_report Write frappe_create_api_endpoint Write frappe_create_app Write frappe_create_doctype

View all 29 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like frappe_list_reports have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the frappe_list_reports tool do? +

List available Frappe reports. It is categorised as a Read tool in the Frappe Dev MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on frappe_list_reports? +

Add a rule in your Intercept YAML policy under the tools section for frappe_list_reports. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Frappe Dev MCP Server MCP server.

What risk level is frappe_list_reports? +

frappe_list_reports is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit frappe_list_reports? +

Yes. Add a rate_limit block to the frappe_list_reports rule in your Intercept 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.

How do I block frappe_list_reports completely? +

Set action: deny in the Intercept policy for frappe_list_reports. 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.

What MCP server provides frappe_list_reports? +

frappe_list_reports is provided by the Frappe Dev MCP Server MCP server (frappe-dev-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Frappe Dev MCP Server