desktop_enable_face_tracking

THE RISK

Medium Risk

Why desktop_enable_face_tracking needs a policy

This tool creates or modifies configuration state (enabling face tracking in a project configuration file) reversibly. It does not execute arbitrary code, delete data, or move money. It is a configuration write operation.

From the tool's definition The tool name includes 'enable' and the description states it modifies '.expanse.json' configuration, which is a configuration file update operation. Face tracking is a capability toggle, not data deletion or code execution.

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

POLICY

How to control desktop_enable_face_tracking

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_enable_face_tracking:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "desktop_enable_face_tracking": {
      "limits": [
        {
          "counter": "desktop_enable_face_tracking_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

desktop_enable_face_tracking stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

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.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More 8th Wall MCP Server tools

Destructive desktop_remove_component Remove a custom component from the project 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

All 64 8th Wall MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about desktop_enable_face_tracking

What does the desktop_enable_face_tracking tool do? +

Enable face tracking in .expanse.json with optional debug mesh. It is categorised as a Write tool in the 8th Wall MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on desktop_enable_face_tracking? +

Register the 8th Wall MCP Server MCP server in PolicyLayer and add a rule for desktop_enable_face_tracking: 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_enable_face_tracking? +

desktop_enable_face_tracking is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit desktop_enable_face_tracking? +

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

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

desktop_enable_face_tracking 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 →