ops_database_change_context
Read columns and indexes for up to four saved MySQL/PostgreSQL/SQLite tables outside the disabled-table list to prepare a reviewable migration or repair script. PostgreSQL table inputs must use canonical schema-qualified identities. This tool never reads rows, writes data, modifies schema or exec...
This record as markdown: /tools/dutydeck/ops-database-change-context.md
What ops_database_change_context does on DutyDeck
AI agents invoke ops_database_change_context to trigger actions in DutyDeck. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why ops_database_change_context is rated High
ops_database_change_context triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs ops_database_change_context 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_change_context, this is the rule to start with:
ops_database_change_context stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_change_context call is checked against it from then on.
Questions about ops_database_change_context
Read columns and indexes for up to four saved MySQL/PostgreSQL/SQLite tables outside the disabled-table list to prepare a reviewable migration or repair script. PostgreSQL table inputs must use canonical schema-qualified identities. This tool never reads rows, writes data, modifies schema or executes a script. Combine the evidence with actual authorized project models, business validation and migration conventions before generating files. Report missing code, constraints and truncated metadata. Deliver preflight, bounded changes, verification and a feasible recovery strategy; generated programs default to dry-run. Do not execute database changes through SSH, Shell, MCP or client libraries. In read-only mode return code blocks; file creation requires a separately available project writing tool.${UNTRUSTED_EVIDENCE}. It is categorised as a Execute tool in the DutyDeck MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DutyDeck MCP server in PolicyLayer and add a rule for ops_database_change_context: 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_change_context is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ops_database_change_context 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_change_context. 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_change_context 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.
Across the catalogue