QUALITY (analytics) — Surface quality trends across consultations.
AI agents call consultation_analytics 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 retrieves and aggregates historical consultation data to display trends and quality metrics. It has no side effects, does not modify any state, and does not trigger external systems. It is a typical Read-category analytics or reporting function. The low severity reflects minimal blast radius—misuse would only expose existing data or produce misleading reports, not cause system changes or data loss.
From the tool's definition Tool name 'consultation_analytics' with description 'Surface quality trends across consultations' indicates data retrieval and analysis only.
Documented attack patterns abuse exactly the kind of access consultation_analytics 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_analytics:
{
"version": "1",
"default": "deny",
"tools": {
"consultation_analytics": {}
}
} consultation_analytics 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.
QUALITY (analytics) — Surface quality trends across consultations. 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_analytics: 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_analytics 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_analytics 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_analytics. 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_analytics 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.