RENDER REPORT — Server-side HTML report rendering. Pulls structured data
AI agents call render_report to retrieve information from Iconsult MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and formats existing structured data into an HTML report for presentation. This is a read operation: it does not create, modify, or delete data; does not execute arbitrary code or shell commands; and does not move money or irreversibly change state. The blast radius of misuse is minimal—worst case is disclosure of information already accessible to the agent or rendering errors.
From the tool's definition Tool name and description indicate 'render_report' performs server-side HTML report rendering that 'pulls structured data' — a read operation with no modification, deletion, or execution of external code.
Documented attack patterns abuse exactly the kind of access render_report gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Iconsult MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for render_report:
{
"version": "1",
"default": "deny",
"tools": {
"render_report": {}
}
}render_report is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
RENDER REPORT — Server-side HTML report rendering. Pulls structured data. It is categorised as a Read tool in the Iconsult MCP MCP Server, which means it retrieves data without modifying state.
Register the Iconsult MCP server in PolicyLayer and add a rule for render_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 Iconsult MCP. Nothing to install.
render_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 render_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_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_report is provided by the Iconsult MCP server (marcus-waldman/iconsult_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Iconsult MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 Iconsult MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.