Complete reference for building Google Play-compliant large screen, tablet, foldable, and ChromeOS apps. Covers: WindowSizeClass (Compact/Medium/Expanded), NavigationSuiteScaffold, ListDetailPaneScaffold (two-pane), foldable hinge detection, continuity across config changes, and Google Play large...
Part of the AndroJack MCP server.
Free to start. No card required.
AI agents call android_large_screen_guide to retrieve information from AndroJack MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though android_large_screen_guide only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"android_large_screen_guide": {}
}
}See the full AndroJack MCP policy for all 22 tools.
These attack patterns abuse exactly the kind of access android_large_screen_guide gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Complete reference for building Google Play-compliant large screen, tablet, foldable, and ChromeOS apps. Covers: WindowSizeClass (Compact/Medium/Expanded), NavigationSuiteScaffold, ListDetailPaneScaffold (two-pane), foldable hinge detection, continuity across config changes, and Google Play large-screen quality tier checklist. Call before building any multi-screen layout, navigation, or when targeting tablets and foldables. Topics: windowsizeclass, navigation, two-pane, foldables, continuity, Play quality.. It is categorised as a Read tool in the AndroJack MCP MCP Server, which means it retrieves data without modifying state.
Register the AndroJack MCP server in PolicyLayer and add a rule for android_large_screen_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_large_screen_guide is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the android_large_screen_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_large_screen_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_large_screen_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.