AI agents use write_text_file to create or update resources in Adb — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adb environment.
This tool creates or modifies text files on an Android device, which is reversible (files can be edited or deleted later). It does not permanently destroy data or execute arbitrary code, so it falls under Write rather than Destructive or Execute.
From the tool's definition Tool name: 'write_text_file'; description: '在设备上创建或覆盖文本文件' (Create or overwrite text file on device). The verb 'write' combined with 'create or overwrite' explicitly indicates data modification capability.
Documented attack patterns abuse exactly the kind of access write_text_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Adb, and nothing reaches the server without passing your rules. This is the rule we recommend for write_text_file:
{
"version": "1",
"default": "deny",
"tools": {
"write_text_file": {
"limits": [
{
"counter": "write_text_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}write_text_file stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
在设备上创建或覆盖文本文件. It is categorised as a Write tool in the Adb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Adb MCP server in PolicyLayer and add a rule for write_text_file: 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 Adb. Nothing to install.
write_text_file 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 write_text_file 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 write_text_file. 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.
write_text_file is provided by the Adb MCP server (wolfcoming/adb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Adb, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
48 Adb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.