START PROJECT — Create or refresh a per-project cache row.
AI agents use start_project 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 writes a new record or updates an existing one in a project cache. It is reversible (cache rows can be overwritten or deleted) and has no destructive, financial, or execution implications. Blast radius is low as it only affects a project metadata cache.
From the tool's definition 'Create or refresh a per-project cache row' — creates or modifies a cache entry for a project
Documented attack patterns abuse exactly the kind of access start_project 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 start_project:
{
"version": "1",
"default": "deny",
"tools": {
"start_project": {
"limits": [
{
"counter": "start_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} start_project 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.
START PROJECT — Create or refresh a per-project cache row. 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 start_project: 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.
start_project 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 start_project 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 start_project. 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.
start_project 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.