ui_assert_gone

Assert element does NOT exist on screen (pass/fail)

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexgladkov-claude-in-mobile/ui-assert-gone.md

WHAT IT DOES

What ui_assert_gone does on Claude Mobile

AI agents use ui_assert_gone to create or update resources in Claude Mobile, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Mobile environment.

RISK

Why ui_assert_gone is rated Medium

An AI agent can call ui_assert_gone faster than any human can review: one bad instruction and it creates or modifies resources in Claude Mobile by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ui_assert_gone safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ui_assert_gone, this is the rule to start with:

ui_assert_gone Rate-limited

ui_assert_gone 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.

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every ui_assert_gone call is checked against it from then on.

FAQ

Questions about ui_assert_gone

What does the ui_assert_gone tool do? +

Assert element does NOT exist on screen (pass/fail). It is categorised as a Write tool in the Claude Mobile MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ui_assert_gone? +

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

What risk level is ui_assert_gone? +

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

Can I rate-limit ui_assert_gone? +

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

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

ui_assert_gone is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Mobile, and thousands of servers like it.

This server

All 198 Claude Mobile tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →