PLAN — Generate an adaptive consultation plan after match_concepts.
AI agents use plan_consultation to create or update resources in Iconsult MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iconsult MCP environment.
This tool creates or synthesizes a consultation plan—a new data structure—in response to architectural analysis. While the plan itself is not executable code and generates no immediate side effects, it represents reversible data creation that could influence subsequent decisions or actions in the consultation workflow.
From the tool's definition Tool name 'plan_consultation' with description 'Generate an adaptive consultation plan' indicates creation of a structured output artifact (a consultation plan).
Documented attack patterns abuse exactly the kind of access plan_consultation 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 plan_consultation:
{
"version": "1",
"default": "deny",
"tools": {
"plan_consultation": {
"limits": [
{
"counter": "plan_consultation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} plan_consultation stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
PLAN — Generate an adaptive consultation plan after match_concepts. It is categorised as a Write tool in the Iconsult MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Iconsult MCP server in PolicyLayer and add a rule for plan_consultation: 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.
plan_consultation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the plan_consultation 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 plan_consultation. 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.
plan_consultation 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.