graph_create_bug
AI agents use graph_create_bug 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.
This tool creates or adds data (a bug) to the system's graph structure, which is a reversible write operation. While the description is uninformative, the naming pattern strongly suggests it creates new records rather than reading, executing external code, destroying data, or moving money. Creation operations are Write category.
From the tool's definition Tool name 'graph_create_bug' indicates creation of a bug record in what appears to be a graph-based system.
Attacks that exploit this kind of access
graph_create_bug. 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_bug: 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_bug 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_bug 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_bug. 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_bug 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 →