AI agents call kotor_installation_info 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 inspects metadata about a Knights of the Old Republic game installation—no side effects, no state changes, no code execution, and no data deletion. It is a straightforward read operation that gathers diagnostic information about an installation's structure and status.
From the tool's definition Tool description states it provides 'installation summary: path, game, valid, errors, missing files, module/override counts' and 'Loads installation if not cached.' These are purely informational queries with no modification, deletion, or execution…
Attacks that exploit this kind of access
Use when you need installation summary: path, game, valid, errors, missing files, module/override counts. Loads installation if not cached. 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 kotor_installation_info: 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.
kotor_installation_info 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 kotor_installation_info 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 kotor_installation_info. 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.
kotor_installation_info 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 →