// SCAN REPORT

Mode Manager MCP

9 tools. 6 can modify or destroy data without limits.

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

Last updated: 12 Jun 2026

6 can modify or destroy data

3 read-only

9 tools total

Community server · catalogue entry verified 12/06/2026

How to control Mode Manager MCP ↓

TOOL MAP

What Mode Manager MCP exposes to your agents

Read (3) Write / Execute (5) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Mode Manager MCP tools

Destructive · High delete_instruction This tool permanently removes instruction files, which cannot be undone. Write · Medium configure_memory_optimization This tool creates or modifies configuration settings reversibly. Write · Medium create_instruction This tool creates or modifies configuration files in the VS Code environment by writing a new .instructions.md file. Write · Medium optimize_memory The tool modifies the contents and organization of a memory file through AI-driven consolidation.

6 of Mode Manager MCP's 9 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Mode Manager MCP

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

Deny destructive operations

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

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

Rate limit write operations

{
  "configure_memory_optimization": {
    "limits": [
      {
        "counter": "configure_memory_optimization_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_instruction": {
    "limits": [
      {
        "counter": "get_instruction_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 Mode Manager MCP — 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 MODE MANAGER →

Free to start. No card required.

FULL CATALOGUE

All 9 Mode Manager MCP tools

DESTRUCTIVE 1 tools

Destructive delete_instruction Delete a VS Code .instructions.md file from the prompts directory.

WRITE 5 tools

Write configure_memory_optimization Configure memory optimization settings for auto-optimization behavior. Write create_instruction Create a new VS Code .instructions.md file with the specified description and content. Write optimize_memory Manually optimize a memory file using AI to reorganize and consolidate entries while preserving all informatio Write remember remember Write update_instruction Update an existing VS Code .instructions.md file with new description or content.

READ 3 tools

Read get_instruction Get the raw content of a VS Code .instructions.md file. Read list_instructions List all VS Code .instructions.md files in the prompts directory. Read memory_stats Get detailed statistics and optimization status for a memory file.

EXPLORE

Related servers

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

FAQ

Questions about Mode Manager MCP

Can an AI agent delete data through the Mode Manager MCP server? +

Yes. The Mode Manager MCP server exposes 1 destructive tools including delete_instruction. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Mode Manager MCP? +

The Mode Manager MCP server has 5 write tools including configure_memory_optimization, create_instruction, optimize_memory. 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 Mode Manager MCP.

How many tools does the Mode Manager MCP server expose? +

9 tools across 3 categories: Destructive, Read, Write. 3 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on Mode Manager MCP? +

Register the Mode Manager 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 Mode Manager MCP tool call.

Deterministic rules across all 9 Mode Manager MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MODE MANAGER →

Free to start. No card required.

9 Mode Manager MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.