Execute DDL (create/drop) in Tsurugi RDBMS.
AI agents call executeDdl to permanently remove resources in Tsurugi Python Mcp Tools — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
DDL operations include DROP statements which permanently delete database structures and all contained data. This is irreversible and has a large blast radius — an AI agent could drop entire tables or schemas. Even CREATE can have destructive implications (e.g., CREATE OR REPLACE). The most severe applicable category is Destructive.
From the tool's definition Execute DDL (create/drop) in Tsurugi RDBMS — explicitly includes 'drop' which irreversibly destroys database objects (tables, schemas, indexes, etc.)
Attacks that exploit this kind of access
Execute DDL (create/drop) in Tsurugi RDBMS. It is categorised as a Destructive tool in the Tsurugi Python Mcp Tools MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tsurugi Python Mcp Tools MCP server in PolicyLayer and add a rule for executeDdl: 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 Tsurugi Python Mcp Tools. Nothing to install.
executeDdl is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the executeDdl 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 executeDdl. 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.
executeDdl is provided by the Tsurugi Python Mcp Tools MCP server (septigram/tsurugi-python-mcp-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →