Create a timestamped session directory for evidence capture. Optionally clears logcat and records device info.
AI agents use android_start_session to create or update resources in DevLab MCP Suite — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DevLab MCP Suite environment.
The primary action is creating a new directory (a reversible write operation). The optional logcat clearing is a minor side effect with low blast radius. No code execution, data deletion, or financial impact is involved.
From the tool's definition Create a timestamped session directory for evidence capture. Optionally clears logcat and records device info.
Attacks that exploit this kind of access
Create a timestamped session directory for evidence capture. Optionally clears logcat and records device info. It is categorised as a Write tool in the DevLab MCP Suite MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DevLab MCP Suite MCP server in PolicyLayer and add a rule for android_start_session: 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.
android_start_session is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the android_start_session 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_start_session. 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_start_session 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →