render_skill_report
Render previously-computed BoQ results into a deliverable (Excel workbook or Word report). Excel is free with watermark + sheet protection; Word is paid-tier only and returns a TIER_INSUFFICIENT envelope for anonymous callers. The wire shape matches POST /api/v1/mcp/render exactly.
This record as markdown: /tools/com-civilquants-civilquants/render-skill-report.md
What render_skill_report does on Civilquants
AI agents invoke render_skill_report to trigger actions in Civilquants. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
request | object | Yes | Wire shape for POST /api/v1/mcp/render. |
Parameters from the server's own tool schema.
Why render_skill_report is rated High
This tool executes a rendering operation that generates files with non-trivial side effects (file creation, format conversion, protection/watermark application). While it operates on previously-computed data (not destructive), it performs external operations whose output depends on arguments and user tier.
From the tool's definition Tool 'render_skill_report' performs rendering operations that generate deliverable files (Excel workbooks or Word reports) with different outputs based on tier status.
Risk signalsAccepts freeform code/query input (request.compute_results[].warnings[].code) · High parameter count (40 properties)
Attacks that exploit this kind of access
The rule that runs render_skill_report safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Civilquants, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For render_skill_report, this is the rule to start with:
render_skill_report stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Civilquants, apply this rule, and every render_skill_report call is checked against it from then on.
Questions about render_skill_report
Render previously-computed BoQ results into a deliverable (Excel workbook or Word report). Excel is free with watermark + sheet protection; Word is paid-tier only and returns a TIER_INSUFFICIENT envelope for anonymous callers. The wire shape matches POST /api/v1/mcp/render exactly. It is categorised as a Execute tool in the Civilquants MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
render_skill_report accepts 1 parameter: request. Required: request. The full parameter table on this page comes from the server's own tool schema.
Register the Civilquants MCP server in PolicyLayer and add a rule for render_skill_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 Civilquants. Nothing to install.
render_skill_report is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the render_skill_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 render_skill_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.
render_skill_report is provided by the Civilquants MCP server (https://api.civilquants.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Civilquants, and thousands of servers like it.
Across the catalogue