list_report_generated
List generated reports for a specific report configuration
This record as markdown: /tools/adbutler/list-report-generated.md
What list_report_generated does on AdButler
AI agents call list_report_generated to retrieve information from AdButler 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 |
|---|---|---|---|
limit | number | — | Max results to return (default 100, max 100) |
offset | number | — | Pagination offset |
report_config_id | number | Yes | Report configuration ID |
Parameters from the server's own tool schema.
Why list_report_generated is rated Low
This tool queries and lists existing generated reports without creating, modifying, or deleting any data. It is a straightforward read operation that has no blast radius if misused by an AI agent—at worst, it would retrieve data the agent is already authorized to access. No financial, destructive, or execute capabilities are present.
From the tool's definition Tool name 'list_report_generated' and description 'List generated reports for a specific report configuration' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_report_generated safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdButler, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_report_generated, this is the rule to start with:
list_report_generated is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every list_report_generated call is checked against it from then on.
Questions about list_report_generated
List generated reports for a specific report configuration. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
list_report_generated accepts 3 parameters: limit, offset, report_config_id. Required: report_config_id. The full parameter table on this page comes from the server's own tool schema.
Register the AdButler MCP server in PolicyLayer and add a rule for list_report_generated: 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 AdButler. Nothing to install.
list_report_generated 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 list_report_generated 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 list_report_generated. 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.
list_report_generated is provided by the AdButler MCP server (adbutler/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue