reset_toast

THE RISK

Low Risk

Why reset_toast needs a policy

The tool name suggests it may reset or clear toast notifications on an Android device. Toast notifications are ephemeral UI messages, so resetting them would likely be a low-impact read/write/clear operation. However, with no description available, confidence is very low.

From the tool's definition Tool name is 'reset_toast' and description is empty or uninformative.

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

POLICY

How to control reset_toast

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reset_toast": {
      "limits": [
        {
          "counter": "reset_toast_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

reset_toast gets a rate cap, and everything else on the server is denied unless you say otherwise.

Create a free account and register uiautomator2 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.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More uiautomator2 MCP Server tools

Destructive app_clear app_clear Destructive app_uninstall app_uninstall Destructive app_uninstall_all app_uninstall_all Destructive clear_text clear_text Destructive purge purge Execute activity_wait_appear activity_wait_appear Execute app_start app_start Execute app_stop app_stop

All 77 uiautomator2 MCP Server tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about reset_toast

What does the reset_toast tool do? +

reset_toast. It is categorised as a Other tool in the uiautomator2 MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on reset_toast? +

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

What risk level is reset_toast? +

reset_toast is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit reset_toast? +

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

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

reset_toast is provided by the uiautomator2 MCP Server MCP server (tanbro/uiautomator2-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every uiautomator2 MCP Server tool call.

Start from uiautomator2 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 →