graph_create_component
AI agents use graph_create_component to create or update resources in IMS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your IMS MCP Server environment.
The tool creates new entities (components) in what appears to be an architectural or system graph, based on sibling tools like 'graph_create_bug', 'graph_create_decision', and 'graph_create_feature'. This is a write operation that modifies stored state reversibly. Confidence is moderate (0.7) because the description is empty and we infer intent from naming convention and sibling tools.
From the tool's definition Tool name 'graph_create_component' indicates creation of a component (likely in a knowledge graph or system model). The 'create' verb signals a write operation that generates new data.
Attacks that exploit this kind of access
graph_create_component. It is categorised as a Write tool in the IMS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the IMS MCP Server MCP server in PolicyLayer and add a rule for graph_create_component: 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 IMS MCP Server. Nothing to install.
graph_create_component 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 graph_create_component 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 graph_create_component. 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.
graph_create_component is provided by the IMS MCP Server MCP server (jdelon02/ims-mcp). 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 →