Create a new DOT graph file
AI agents use create_graph to create or update resources in ContextForge MCP Gateway — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ContextForge MCP Gateway environment.
This tool creates new data (a DOT graph file) in a reversible manner. File creation is a Write-category operation. Severity is low because DOT graph files are typically non-critical data structures used for visualization/diagramming, with minimal blast radius if misused by an agent. The operation is reversible (the file can be deleted or overwritten).
From the tool's definition Tool name 'create_graph' and description 'Create a new DOT graph file' indicate file creation. The tool creates a new artifact (DOT graph file) without deleting or destroying existing data, and does not execute arbitrary code or manage financial resources.
Attacks that exploit this kind of access
Create a new DOT graph file. It is categorised as a Write tool in the ContextForge MCP Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for create_graph: 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 ContextForge MCP Gateway. Nothing to install.
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 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 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 ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →