graph_impact_analysis
AI agents call graph_impact_analysis to retrieve information from IMS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name suggests an analysis/read operation that examines impact relationships in a graph (e.g., dependency or change impact analysis). Analysis tools are typically read-only queries. However, with no description, confidence is low. Severity is medium because in an IMS context, impact analysis could surface sensitive architectural or dependency information.
From the tool's definition Tool name 'graph_impact_analysis' — no description provided.
Attacks that exploit this kind of access
graph_impact_analysis. It is categorised as a Read tool in the IMS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the IMS MCP Server MCP server in PolicyLayer and add a rule for graph_impact_analysis: 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_impact_analysis is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the graph_impact_analysis 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_impact_analysis. 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_impact_analysis 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 →