// SCAN REPORT

MTA:SA Documentation MCP Server

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

1 destructive tool with no built-in limits. Policy required.

Last updated: 28 Jun 2026

1 can modify or destroy data

10 read-only

11 tools total

Community server · catalogue entry verified 28/06/2026

How to control MTA:SA Documentation MCP Server ↓

TOOL MAP

What MTA:SA Documentation MCP Server exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous MTA:SA Documentation MCP Server tools

Destructive · Low clear_cache Clearing a cache irreversibly removes cached data, requiring it to be rebuilt.

1 of MTA:SA Documentation MCP Server's 11 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control MTA:SA Documentation MCP Server

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

Deny destructive operations

{
  "clear_cache": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Cap read operations

{
  "find_events_for_task": {
    "limits": [
      {
        "counter": "find_events_for_task_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

Create a free account and register MTA:SA Documentation MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MTA:SA DOCUMENTATION →

Instant setup, no code required.

FULL CATALOGUE

All 11 MTA:SA Documentation MCP Server tools

DESTRUCTIVE 1 tools

Destructive clear_cache Clear the MTA:SA documentation cache for a specific function or all functions.

READ 10 tools

Read find_events_for_task Task-to-events matcher. Use when you need event names for handlers/triggers (e.g., resource lifecycle, player Read find_functions_for_task Task-to-functions matcher. Use this FIRST when user intent is high-level (e.g., Read get_cache_stats Get statistics about the MTA:SA documentation cache. Read get_function_docs Fetch authoritative docs for exactly ONE MTA:SA function/event by canonical name. Preferred over manual web br Read get_function_examples Get only code examples for one function/event after docs lookup. Use when writing implementation snippets and Read get_multiple_function_docs Batch docs retrieval for implementation phase. Provide exact function/event names (ideally from search/find to Read list_functions_by_category Enumerate canonical function/event names in a category. Useful for discovery when query terms are vague. Read recommend_doc_workflow Planner tool that tells LLMs exactly which mtasa-docs tools to call next for a given task. Use this to enforce Read search_events Event discovery tool. Search MTA:SA client/server events only (not regular functions), then chain into docs to Read search_functions Primary discovery tool. Search MTA:SA functions and events by name or keyword before coding. Returns canonical

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about MTA:SA Documentation MCP Server

Can an AI agent delete data through the MTA:SA Documentation MCP Server MCP server? +

Yes. The MTA:SA Documentation MCP Server server exposes 1 destructive tools including clear_cache. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How many tools does the MTA:SA Documentation MCP Server MCP server expose? +

11 tools across 2 categories: Destructive, Read. 10 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on MTA:SA Documentation MCP Server? +

Register the MTA:SA Documentation MCP Server 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 MTA:SA Documentation MCP Server tool call.

Deterministic rules across all 11 MTA:SA Documentation MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MTA:SA DOCUMENTATION →

Instant setup, no code required.

11 MTA:SA Documentation MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// WHERE THIS COMES FROM

These policies come from MTA:SA Documentation MCP Server's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →