adb_file_touch
Create an empty file or update timestamps. Three modes: create (touch non-existent path), update (set atime/mtime to now), or set explicit timestamp. On FAT32, timestamps have 2-second resolution. On tmpfs, timestamps are volatile.
This record as markdown: /tools/io-github-fullread-deepadb/adb-file-touch.md
What adb_file_touch does on Deepadb
AI agents use adb_file_touch 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_file_touch is rated Medium
This tool creates new files or modifies existing file timestamps. File creation and metadata modification are reversible write operations — files can be deleted and timestamps reset. It does not execute code, delete data irreversibly, or involve financial transactions.
From the tool's definition Tool description states it can "Create an empty file or update timestamps" with three modes including "create (touch non-existent path)" and "update (set atime/mtime to now)". These are write operations that create or modify file metadata.
Attacks that exploit this kind of access
The rule that runs adb_file_touch 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_file_touch, this is the rule to start with:
adb_file_touch 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_file_touch call is checked against it from then on.
Questions about adb_file_touch
Create an empty file or update timestamps. Three modes: create (touch non-existent path), update (set atime/mtime to now), or set explicit timestamp. On FAT32, timestamps have 2-second resolution. On tmpfs, timestamps are volatile. 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_file_touch: 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_file_touch 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_file_touch 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_file_touch. 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_file_touch 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