get_report_results
Use this when the user wants to retrieve the data results of a specific saved report. Uses the report's saved time range, resolved at execution for relative ranges. Accepts an ID or a case-insensitive substring name lookup within the first 200 newest reports; multiple matches return an ambiguity ...
This record as markdown: /tools/doit/get-report-results.md
What get_report_results does on Doit
AI agents call get_report_results to retrieve information from Doit 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 |
|---|---|---|---|
id | string | — | The ID of the report to retrieve results for. |
name | string | — | Case-insensitive substring lookup within the first 200 newest reports only. Multiple matches return an ambiguity error; id takes precedence when both are provid |
Parameters from the server's own tool schema.
Why get_report_results is rated Low
Even though get_report_results 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.
Attacks that exploit this kind of access
The rule that runs get_report_results safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Doit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_report_results, this is the rule to start with:
get_report_results 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 Doit, apply this rule, and every get_report_results call is checked against it from then on.
Questions about get_report_results
Use this when the user wants to retrieve the data results of a specific saved report. Uses the report's saved time range, resolved at execution for relative ranges. Accepts an ID or a case-insensitive substring name lookup within the first 200 newest reports; multiple matches return an ambiguity error and id takes precedence. Do NOT use this for listing all reports (use list_reports) or running ad-hoc queries (use run_query). It is categorised as a Read tool in the Doit MCP Server, which means it retrieves data without modifying state.
get_report_results accepts 2 parameters: id, name. The full parameter table on this page comes from the server's own tool schema.
Register the Doit MCP server in PolicyLayer and add a rule for get_report_results: 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 Doit. Nothing to install.
get_report_results 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_report_results 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_report_results. 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_report_results is provided by the Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Doit, and thousands of servers like it.
This server
Across the catalogue