BUILD PROJECT KG — Build the per-project canonical layer for
AI agents use build_project_kg 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.
Building a per-project canonical knowledge graph layer is a Write operation: it creates and stores structured data. It is reversible in principle (the KG can be rebuilt or deleted), so it doesn't reach Destructive. The blast radius is medium — a misconfigured KG could corrupt architecture recommendations for the project, but the scope is limited to a single project's consulting data.
From the tool's definition 'BUILD PROJECT KG — Build the per-project canonical layer' — creates/builds a knowledge graph structure for a project
Documented attack patterns abuse exactly the kind of access build_project_kg 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 build_project_kg:
{
"version": "1",
"default": "deny",
"tools": {
"build_project_kg": {
"limits": [
{
"counter": "build_project_kg_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} build_project_kg 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.
BUILD PROJECT KG — Build the per-project canonical layer for. 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 build_project_kg: 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.
build_project_kg 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 build_project_kg 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 build_project_kg. 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.
build_project_kg 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.