Reinicia um emulador (kill + start) com opções de boot e telemetria de duração.
AI agents invoke avd_restart to trigger actions in AVD MCP Server. 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.
This tool triggers external operations (kill and restart processes) on the AVD emulator, which are side effects that modify the state of running systems. It is not merely querying data (Read), nor is it persistently creating/modifying stored data (Write). The restart operation with configurable boot options and telemetry makes it an Execute action.
From the tool's definition Tool description states it 'Reinicia um emulador (kill + start)' - restarts an Android Virtual Device emulator by killing and starting it.
Attacks that exploit this kind of access
Reinicia um emulador (kill + start) com opções de boot e telemetria de duração. It is categorised as a Execute tool in the AVD MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AVD MCP Server MCP server in PolicyLayer and add a rule for avd_restart: 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 AVD MCP Server. Nothing to install.
avd_restart 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 avd_restart 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 avd_restart. 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.
avd_restart is provided by the AVD MCP Server MCP server (jramalho/avd-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 →