list_reports

列出某使用者的 Bug 報告（需提供 user_email + session_token 驗證身分）。List a user's bug reports — requires user_email and session_token.

SERVERBugEzy SOURCEhttps://bugezy.dev/mcp

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/dev-bugezy-bugezy/list-reports.md

WHAT IT DOES

What list_reports does on BugEzy

AI agents call list_reports to retrieve information from BugEzy without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`url`	string	—
`limit`	number	—
`user_email`	string	—	使用者 email；只回傳該 email 的報告。未提供則不回任何報告（安全預設）。
`session_token`	string	—	BugEzy session token（如果 MCP URL 已帶 ?token= 則不需提供）。

Parameters from the server's own tool schema.

RISK

Why list_reports is rated Low

Even though list_reports only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_reports safely

PolicyLayer is an MCP gateway: it sits between your AI agents and BugEzy, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_reports, this is the rule to start with:

list_reports Allowed

list_reports is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_reports": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect BugEzy, apply this rule, and every list_reports call is checked against it from then on.

FAQ

Questions about list_reports

What does the list_reports tool do? +

列出某使用者的 Bug 報告（需提供 user_email + session_token 驗證身分）。List a user's bug reports — requires user_email and session_token. It is categorised as a Read tool in the BugEzy MCP Server, which means it retrieves data without modifying state.

What parameters does list_reports accept? +

list_reports accepts 4 parameters: url, limit, user_email, session_token. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_reports? +

Register the BugEzy MCP server in PolicyLayer and add a rule for list_reports: 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 BugEzy. Nothing to install.

What risk level is list_reports? +

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

Can I rate-limit list_reports? +

Yes. Add a rate_limit block to the list_reports 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.

How do I block list_reports completely? +

Set action: deny in the PolicyLayer policy for 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 list_reports? +

list_reports is provided by the BugEzy MCP server (https://bugezy.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on BugEzy, and thousands of servers like it.

This server

All 13 BugEzy tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →