Wear OS development reference — Wear OS 5 (API 35), Material 3 Expressive for Wear (stable Aug 2025). CRITICAL: Wear OS uses DIFFERENT Compose dependencies than phone apps. AI tools generate phone Compose (LazyColumn, Button, NavHost) — none of these compile on Wear OS. Correct Wear components: S...
Part of the AndroJack MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke android_wearos_guide to trigger processes or run actions in AndroJack MCP. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
android_wearos_guide can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
android_wearos_guide:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full AndroJack MCP policy for all 22 tools.
Agents calling execute-class tools like android_wearos_guide have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
android_wearos_guide is one of the high-risk operations in AndroJack MCP. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Wear OS development reference — Wear OS 5 (API 35), Material 3 Expressive for Wear (stable Aug 2025). CRITICAL: Wear OS uses DIFFERENT Compose dependencies than phone apps. AI tools generate phone Compose (LazyColumn, Button, NavHost) — none of these compile on Wear OS. Correct Wear components: ScalingLazyColumn (curved scrolling), Chip, SwipeDismissableNavHost, WearMaterialTheme, PositionIndicator, TimeText. Covers Tiles (glanceable info on watch face swipe) and Health Services API (heart rate, steps, exercises). Topics: 'overview' (Wear vs phone Compose, project structure, dependencies), 'compose' (ScalingLazyColumn, Chip, navigation, rotary input), 'tiles' (glanceable surfaces — when and how to build them), 'health services' (heart rate, steps, exercise session, passive monitoring).. It is categorised as a Execute tool in the AndroJack MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for android_wearos_guide. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AndroJack MCP MCP server.
android_wearos_guide is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the android_wearos_guide rule in your Intercept 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.
Set action: deny in the Intercept policy for android_wearos_guide. 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.
android_wearos_guide is provided by the AndroJack MCP MCP server (androjack-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept