get_ai_report
Generate an AI analysis report for a survey's responses. Returns executive summary, key metrics, per-question insights, and action recommendations.
This record as markdown: /tools/com-getinquira-inquira/get-ai-report.md
What get_ai_report does on Inquira
AI agents call get_ai_report to retrieve information from Inquira 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 |
|---|---|---|---|
survey_id | string | Yes | The ID of the survey to analyze. |
Parameters from the server's own tool schema.
Why get_ai_report is rated Low
This tool reads existing survey response data and produces an analytical summary. It does not create, modify, delete, or execute operations; it purely derives insights from already-collected responses. The analysis generation is a computational read operation with no side effects on the survey system or external services.
From the tool's definition Tool description states it "Generate[s] an AI analysis report" and "Returns executive summary, key metrics, per-question insights, and action recommendations." The verb pattern and output description indicate data retrieval and synthesis (report generation)…
Attacks that exploit this kind of access
The rule that runs get_ai_report safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Inquira, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_ai_report, this is the rule to start with:
get_ai_report 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 Inquira, apply this rule, and every get_ai_report call is checked against it from then on.
Questions about get_ai_report
Generate an AI analysis report for a survey's responses. Returns executive summary, key metrics, per-question insights, and action recommendations. It is categorised as a Read tool in the Inquira MCP Server, which means it retrieves data without modifying state.
get_ai_report accepts 1 parameter: survey_id. Required: survey_id. The full parameter table on this page comes from the server's own tool schema.
Register the Inquira MCP server in PolicyLayer and add a rule for get_ai_report: 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 Inquira. Nothing to install.
get_ai_report 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_ai_report 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_ai_report. 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_ai_report is provided by the Inquira MCP server (https://getinquira.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Inquira, and thousands of servers like it.
This server
Across the catalogue