android_open_app_settings · DevLab MCP Suite MCP

WHAT IT DOES

What android_open_app_settings does on DevLab MCP Suite

AI agents invoke android_open_app_settings to trigger actions in DevLab MCP Suite. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why android_open_app_settings needs a policy

This tool triggers an external operation on the Android device by firing a system intent to navigate to a specific settings screen. It does not merely read data nor does it delete/modify data itself, but it executes an Android intent action that affects the device's UI state and could facilitate further destructive actions (e.g., clearing data, revoking permissions) from the opened settings screen.

From the tool's definition 'Open the system Settings > App Info screen for a given package. Uses android.settings.APPLICATION_DETAILS_SETTINGS intent.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

android_open_app_settings Rate-limited

android_open_app_settings stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "android_open_app_settings": {
      "limits": [
        {
          "counter": "android_open_app_settings_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches DevLab MCP Suite, so you can run agents against it safely.

FAQ

Questions about android_open_app_settings

What does the android_open_app_settings tool do? +

Open the system Settings > App Info screen for a given package. Uses android.settings.APPLICATION_DETAILS_SETTINGS intent. It is categorised as a Execute tool in the DevLab MCP Suite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on android_open_app_settings? +

Register the DevLab MCP Suite MCP server in PolicyLayer and add a rule for android_open_app_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 DevLab MCP Suite. Nothing to install.

What risk level is android_open_app_settings? +

android_open_app_settings is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit android_open_app_settings? +

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

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

android_open_app_settings is provided by the DevLab MCP Suite MCP server (tanguito86/devlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.