AI agents call getInstallationGraph to retrieve information from KotorMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and iterates through pre-computed graph data from a snapshot already loaded in memory. It performs no side effects, creates no new resources, executes no external operations, and cannot modify or delete game installation data. It is a pure read operation for dependency analysis of KOTOR game resources.
From the tool's definition The tool 'pages through canonical dependency edges extracted from an in-memory installation snapshot.' The description explicitly indicates reading/querying existing data structures (dependency edges) with no modification, creation, or deletion capability…
Attacks that exploit this kind of access
Page through canonical dependency edges extracted from an in-memory installation snapshot created by openInstallation. It is categorised as a Read tool in the KotorMCP MCP Server, which means it retrieves data without modifying state.
Register the Kotor MCP server in PolicyLayer and add a rule for getInstallationGraph: 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 KotorMCP. Nothing to install.
getInstallationGraph 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 getInstallationGraph 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 getInstallationGraph. 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.
getInstallationGraph is provided by the Kotor MCP server (th3w1zard1/kotormcp). 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 →