clear_settings

THE RISK

Critical Risk

Why clear_settings needs a policy

The tool explicitly clears settings and cached data, which is an irreversible operation that destroys existing configuration state. This qualifies as Destructive rather than Write because the action cannot be reversed through normal operations. While the blast radius may be limited to the server's own state (high rather than critical), the operation is fundamentally destructive.

From the tool's definition Tool name 'clear_settings' combined with description 'Clear all settings and cached data' indicates irreversible deletion of configuration and cached state. This cannot be undone without manual reconfiguration.

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access clear_settings gives an agent:

POLICY

How to control clear_settings

PolicyLayer is an MCP gateway — it sits between your AI agents and Code Index, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_settings:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_settings"
  ]
}

clear_settings disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Code Index — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Code Index tools

Execute build_deep_index Build the deep index (full symbol extraction) for the current project. This performs Execute refresh_index Manually rebuild the project file index. Use after git operations or when index seems stal Execute refresh_search_tools Manually re-detect the available command-line search tools on the system. This is usef Write configure_file_watcher configure_file_watcher Write create_temp_directory Create the temporary directory used for storing index data. Write set_project_path Set the base project path for indexing. Read check_temp_directory Check the temporary directory used for storing index data. Read find_files Find files matching glob pattern using in-memory index. Supports path patterns (.py, test_

All 14 Code Index tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Code Index → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about clear_settings

What does the clear_settings tool do? +

Clear all settings and cached data. It is categorised as a Destructive tool in the Code Index MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on clear_settings? +

Register the Code Index MCP server in PolicyLayer and add a rule for clear_settings: 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 Code Index. Nothing to install.

What risk level is clear_settings? +

clear_settings is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clear_settings? +

Yes. Add a rate_limit block to the clear_settings 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.

How do I block clear_settings completely? +

Set action: deny in the PolicyLayer policy for clear_settings. 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.

What MCP server provides clear_settings? +

clear_settings is provided by the Code Index MCP server (johnhuang316/code-index-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Code Index tool call.

Start from Code Index, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →