adb_test_gen_save
Save a generated workflow JSON to the workflows directory for later execution with adb_workflow_run.
This record as markdown: /tools/io-github-fullread-deepadb/adb-test-gen-save.md
What adb_test_gen_save does on Deepadb
AI agents use adb_test_gen_save 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_test_gen_save is rated Medium
This tool writes a file (workflow JSON) to a directory on the system. It is a reversible write operation — the file can be deleted later. However, the saved workflow could later be executed (via adb_workflow_run), making misuse a concern, but the tool itself only performs a write/create action.
From the tool's definition 'Save a generated workflow JSON to the workflows directory'
Attacks that exploit this kind of access
The rule that runs adb_test_gen_save 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_test_gen_save, this is the rule to start with:
adb_test_gen_save 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_test_gen_save call is checked against it from then on.
Questions about adb_test_gen_save
Save a generated workflow JSON to the workflows directory for later execution with adb_workflow_run. 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_test_gen_save: 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_test_gen_save 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_test_gen_save 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_test_gen_save. 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_test_gen_save 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