COVERAGE CHECK — Compute coverage metrics for a consultation session.
AI agents call consultation_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.
This tool queries or derives metrics from an existing consultation session to produce a report. Computing and presenting coverage metrics is a read operation with no side effects—it retrieves or analyzes data without changing state, executing external commands, or creating irreversible changes. Even if the report is generated on-the-fly, the underlying data remains unmodified.
From the tool's definition Tool name 'consultation_report' with description 'COVERAGE CHECK — Compute coverage metrics for a consultation session' indicates a metrics computation and reporting function. The verb 'compute' and noun 'metrics' align with data retrieval and analysis.
Documented attack patterns abuse exactly the kind of access consultation_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 consultation_report:
{
"version": "1",
"default": "deny",
"tools": {
"consultation_report": {}
}
} consultation_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.
COVERAGE CHECK — Compute coverage metrics for a consultation session. 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 consultation_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.
consultation_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 consultation_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 consultation_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.
consultation_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.