Create a new knowledge graph. Supports multiple graph types such as topology, timeline, changelog, requirement documentation, etc. Design guidelines for each graph type: - topology: Used to represent dependencies between system components and modules. Recommended to first create main module nodes...
Part of the Knowledge Graph Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use create_graph to create or modify resources in Knowledge Graph Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call create_graph repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Knowledge Graph Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
create_graph:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Knowledge Graph Server policy for all 15 tools.
Agents calling write-class tools like create_graph have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Create a new knowledge graph. Supports multiple graph types such as topology, timeline, changelog, requirement documentation, etc. Design guidelines for each graph type: - topology: Used to represent dependencies between system components and modules. Recommended to first create main module nodes, then add component nodes, and finally represent relationships through edges like calls, dependencies, and containment - timeline: Used to record important project events and decisions. Recommended to add event nodes in chronological order and link related personnel and decisions - changelog: Used to track change history of features and components. Recommended to create nodes for each significant change, marking change types and impact scope - requirement: Used for requirement management and tracking. Recommended to first create high-level requirements, then break down into specific features, and finally link to responsible persons and iterations - knowledge_base: Used to build domain knowledge systems. Recommended to start from core concepts and gradually expand related concepts and relationships - ontology: Used for formal representation of domain concepts and relationships, suitable for building standardized knowledge models. It is categorised as a Write tool in the Knowledge Graph Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for create_graph. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Knowledge Graph Server MCP server.
create_graph 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 create_graph rule in your Intercept 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 Intercept policy for create_graph. 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.
create_graph is provided by the Knowledge Graph Server MCP server (aiuluna/knowledge-graph-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept