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 server.
Free to start. No card required.
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. PolicyLayer 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.
{
"version": "1",
"default": "deny",
"tools": {
"android_wearos_guide": {
"limits": [
{
"counter": "android_wearos_guide_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full AndroJack MCP policy for all 22 tools.
These attack patterns abuse exactly the kind of access android_wearos_guide gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
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.
Register the AndroJack MCP server in PolicyLayer and add a rule for android_wearos_guide: 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 AndroJack MCP. Nothing to install.
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 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.
Set action: deny in the PolicyLayer 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 server (VIKAS9793/androjack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 22 AndroJack MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.