ims_graph_create_relationship
AI agents use ims_graph_create_relationship 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 'create' prefix and graph context suggest this tool creates new relationships in the IMS graph backend, modifying stored data reversibly. Without a description, confidence is reduced, but the naming pattern and sibling tools (graph_create_bug, graph_create_component, graph_create_decision) establish Write as the appropriate category.
From the tool's definition Tool name 'ims_graph_create_relationship' contains 'create_relationship', indicating data creation/modification in a graph structure. Description is empty, limiting confidence. Sibling tools show this server manages memory graphs and architectural data.
Attacks that exploit this kind of access
ims_graph_create_relationship. 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 ims_graph_create_relationship: 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.
ims_graph_create_relationship 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 ims_graph_create_relationship 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 ims_graph_create_relationship. 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.
ims_graph_create_relationship 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 →