// SCAN REPORT

KotorMCP

28 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated:

1 can modify or destroy data
27 read-only
28 tools total

Community server · catalogue entry verified 30/06/2026

How to control KotorMCP ↓

TOOL MAP

What KotorMCP exposes to your agents

Read (27) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS
High Risk

The most dangerous KotorMCP tools

Write · Medium kotor_extract_resource This tool writes data to the filesystem, which is a Write operation.

1 of KotorMCP's 28 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control KotorMCP

PolicyLayer is an MCP gateway — it sits between your AI agents and KotorMCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations
{
  "kotor_extract_resource": {
    "limits": [
      {
        "counter": "kotor_extract_resource_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "describeResource": {
    "limits": [
      {
        "counter": "describeresource_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register KotorMCP — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON KOTORMCP →

Instant setup, no code required.

FULL CATALOGUE

All 28 KotorMCP tools

WRITE 1 tools
Write kotor_extract_resource Use when you need to write a resolved resource to disk. Optional
READ 27 tools
Read describeResource Use when you need a short summary of a resource (GFF, TLK, 2DA) using resolution order. Read-only. Read detectInstallations Use when you need to discover candidate K1/K2 installation paths (env vars and platform defaults). Read-only. Read getInstallationGraph Page through canonical dependency edges extracted from an in-memory installation snapshot created by openInsta Read getInstallationSnapshot Page through a compacted in-memory installation snapshot created by openInstallation. Use includeData=true for Read journalOverview Use when you need a summary of global.jrl plot categories and entries for the installation. Read-only. Read kotor_describe_dlg Use when you need DLG structure: entry/reply counts and script/condition refs. Read-only. Read kotor_describe_jrl Use when you need a JRL (journal) summary: categories and entries. Read-only. Read kotor_describe_module Use when you need full module analysis: ARE, LYT rooms, WOK list, resource counts, scripts. Read-only. Read kotor_describe_resource_refs Use when you need a reference summary for any GFF resource (scripts, conversations, tags, template resrefs). R Read kotor_find_referrers Use when you need to find which resources reference a script resref, tag, conversation, or resref. Use module_ Read kotor_find_resource Use when you need the first match for a resref or to see all locations. Supports glob (e.g. 203tel). Resolutio Read kotor_find_strref_referrers Use when you need to find which resources use a TLK strref (TLK/2DA Find References parity). Read-only. Read kotor_installation_info Use when you need installation summary: path, game, valid, errors, missing files, module/override counts. Load Read kotor_list_archive Use when you need to list contents of a KEY/BIF/RIM/ERF/MOD file with pagination. Read-only. Read kotor_list_modules Use when you need all modules with human-readable area names (from ARE + TalkTable). Read-only. Read kotor_list_references Use when tracing what a resource references: list outbound refs (scripts, conversations, tags, template resref Read kotor_lookup_2da Use when you need to query a 2DA table by row index, column name, or value search. Read-only. Read kotor_lookup_tlk Use when you need to resolve a strref to display text from dialog.tlk. Read-only. Read kotor_module_resources Use when you need a paginated list of all resources in a module (.rim + _s.rim + _dlg.erf). Read-only. Read kotor_read_2da Use when you need a 2DA table as JSON with optional row range and column filter. Read-only. Read kotor_read_gff Use when you need the full GFF tree as JSON (DLG, UTC, ARE, etc.). Use field_paths or max_depth/max_fields to Read kotor_read_tlk Use when you need TLK (dialog.tlk) entries by strref range or text search. Read-only. Read kotor_search_resources Use when you need to search resource names by regex. Paginated; prefer location/type filter on large installs. Read kotor_walkmesh_validation_diagram Get a text validation diagram for a walkmesh (BWM/WOK): perimeter, transitions, outer boundary. Use when you n Read listResources Use when exploring installation contents: list resources from override/modules/chitin with optional filters. R Read loadInstallation Use when you need to activate an installation in memory for subsequent tools. Read-only; does not modify disk. Read openInstallation Build or reuse a compacted in-memory installation snapshot and return a handle for paged follow-up queries. Re
FAQ

Questions about KotorMCP

How do I prevent bulk modifications through KotorMCP? +

The KotorMCP server has 1 write tools including kotor_extract_resource. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach KotorMCP.

How many tools does the Kotor MCP server expose? +

28 tools across 2 categories: Read, Write. 27 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on KotorMCP? +

Register the Kotor MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every KotorMCP tool call.

Deterministic rules across all 28 KotorMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON KOTORMCP →

Instant setup, no code required.

28 KotorMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.