UPDATE STEP — Update the status of a step in an implementation plan.
AI agents use update_plan_step 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 modifies existing plan data (changing step status) but does not delete, irreversibly overwrite, execute arbitrary code, or commit financial transactions. Status updates to implementation plans are reversible—prior states can be restored, corrections made, or rollbacks performed. The scope is limited to metadata/state within the consultation system.
From the tool's definition Tool description states 'Update the status of a step in an implementation plan.' The verb 'update' and explicit mention of status modification indicate reversible data change rather than deletion or execution of external operations.
Documented attack patterns abuse exactly the kind of access update_plan_step 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 update_plan_step:
{
"version": "1",
"default": "deny",
"tools": {
"update_plan_step": {
"limits": [
{
"counter": "update_plan_step_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_plan_step 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.
UPDATE STEP — Update the status of a step in an implementation plan. 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 update_plan_step: 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.
update_plan_step 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 update_plan_step 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 update_plan_step. 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.
update_plan_step 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.