SHARED STATE (write) — Upsert a key-value pair in consultation shared
AI agents use write_state 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 modifies consultation state data reversibly. It is not destructive (data can be overwritten), not financial, and not executing arbitrary code—it simply persists key-value pairs. The severity is medium because misuse could corrupt consultation session state affecting downstream analysis, but the impact is scoped to a single consultation's shared state and remains reversible.
From the tool's definition Tool name 'write_state' with description 'Upsert a key-value pair in consultation shared' indicates creation or modification of data. 'Upsert' (update or insert) is a reversible write operation that modifies shared state within a consultation session.
Documented attack patterns abuse exactly the kind of access write_state 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 write_state:
{
"version": "1",
"default": "deny",
"tools": {
"write_state": {
"limits": [
{
"counter": "write_state_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}write_state 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.
SHARED STATE (write) — Upsert a key-value pair in consultation shared. 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 write_state: 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.
write_state 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 write_state 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 write_state. 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.
write_state 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.