desktop_remove_component

THE RISK

Critical Risk

Why desktop_remove_component needs a policy

The tool removes a component from the project, which is an irreversible deletion operation. Removing a custom component could break AR experiences that depend on it and cannot be easily undone, making it destructive with high severity.

From the tool's definition Remove a custom component from the project

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

POLICY

How to control desktop_remove_component

PolicyLayer is an MCP gateway — it sits between your AI agents and 8th Wall MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for desktop_remove_component:

policy.json

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

desktop_remove_component 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 8th Wall MCP Server — 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 8th Wall MCP Server tools

Destructive project_delete_file Delete a file under PROJECT_ROOT Execute devserver_start Start a static file server for PROJECT_ROOT Execute devserver_stop Stop the static file server Execute generate_custom_javascript ⚠️ WEB PROJECTS ONLY - NOT FOR DESKTOP! Generate A-Frame components for web-based projects Write assets_download_url Download a file by URL into project/assets/ Write apply_experience_template Apply a pre-configured AR experience template. This automatically sets up components, code Write assets_unzip Unzip a .zip file into project assets directory Write create_ar_experience Create a complete AR experience from a natural language description. This tool automatical

All 64 8th Wall MCP Server 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 8th Wall MCP Server → 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 desktop_remove_component

What does the desktop_remove_component tool do? +

Remove a custom component from the project. It is categorised as a Destructive tool in the 8th Wall MCP Server 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 desktop_remove_component? +

Register the 8th Wall MCP Server MCP server in PolicyLayer and add a rule for desktop_remove_component: 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 8th Wall MCP Server. Nothing to install.

What risk level is desktop_remove_component? +

desktop_remove_component 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 desktop_remove_component? +

Yes. Add a rate_limit block to the desktop_remove_component 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 desktop_remove_component completely? +

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

desktop_remove_component is provided by the 8th Wall MCP Server MCP server (superdwayne/8thwallmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every 8th Wall MCP Server tool call.

Start from 8th Wall MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →