ops_database_write
对已保存的直连 MySQL、本地 SQLite 或已连接 SSH 主机上的 SQLite 文件执行有界写入脚本。每次执行前必须由用户在 Agent 原生确认弹窗中批准，完全自动模式也不能跳过，不需要额外的服务器 Agent 授权。目标限于指定业务库且不得引用禁用表；脚本会记录审计，结果为 committed、rolled-back、partial 或 unknown。partial/unknown 必须先核对实际数据，禁止自动重试。PostgreSQL 与 SSH MySQL/Redis 写入不可用。${UNTRUSTED_EVIDENCE}
This record as markdown: /tools/dutydeck/ops-database-write.md
What ops_database_write does on DutyDeck
AI agents use ops_database_write to create or update resources in DutyDeck, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DutyDeck environment.
Why ops_database_write is rated Medium
An AI agent can call ops_database_write faster than any human can review: one bad instruction and it creates or modifies resources in DutyDeck by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs ops_database_write safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DutyDeck, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ops_database_write, this is the rule to start with:
ops_database_write 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 DutyDeck, apply this rule, and every ops_database_write call is checked against it from then on.
Questions about ops_database_write
对已保存的直连 MySQL、本地 SQLite 或已连接 SSH 主机上的 SQLite 文件执行有界写入脚本。每次执行前必须由用户在 Agent 原生确认弹窗中批准，完全自动模式也不能跳过，不需要额外的服务器 Agent 授权。目标限于指定业务库且不得引用禁用表；脚本会记录审计，结果为 committed、rolled-back、partial 或 unknown。partial/unknown 必须先核对实际数据，禁止自动重试。PostgreSQL 与 SSH MySQL/Redis 写入不可用。${UNTRUSTED_EVIDENCE}. It is categorised as a Write tool in the DutyDeck MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DutyDeck MCP server in PolicyLayer and add a rule for ops_database_write: 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 DutyDeck. Nothing to install.
ops_database_write 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 ops_database_write 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 ops_database_write. 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.
ops_database_write is provided by the DutyDeck MCP server (taokoplay/DutyDeck). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DutyDeck, and thousands of servers like it.
This server
Across the catalogue