adb_mkdir
Create a directory on the device. Supports -p flag for creating parent directories.
This record as markdown: /tools/io-github-fullread-deepadb/adb-mkdir.md
What adb_mkdir does on Deepadb
AI agents use adb_mkdir to create or update resources in Deepadb, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Deepadb environment.
Why adb_mkdir is rated Medium
Directory creation is a reversible write operation that modifies the filesystem by adding new directory entries. It is not destructive (directories can be deleted), does not execute arbitrary code, and carries minimal blast radius on an Android device where directory creation is a common operational task.
From the tool's definition Tool description explicitly states 'Create a directory on the device', which is a write operation that creates data structures (directories) on the target system.
Attacks that exploit this kind of access
The rule that runs adb_mkdir safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_mkdir, this is the rule to start with:
adb_mkdir 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_mkdir call is checked against it from then on.
Questions about adb_mkdir
Create a directory on the device. Supports -p flag for creating parent directories. It is categorised as a Write tool in the Deepadb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_mkdir: 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 Deepadb. Nothing to install.
adb_mkdir 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 adb_mkdir 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 adb_mkdir. 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.
adb_mkdir is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadb, and thousands of servers like it.
This server
Across the catalogue