Revoke schema privileges from a role
AI agents call db_revoke_schema to permanently remove resources in Database MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While not deleting data directly, revoking schema privileges is an irreversible action that fundamentally alters system state and access control in a way that cannot be undone through normal reversal procedures. This fits the Destructive category as the operation removes permissions that were previously granted, and restoring them requires administrative action.
From the tool's definition Tool is named 'db_revoke_schema' and described as 'Revoke schema privileges from a role'. Revoking privileges is an irreversible permission operation that removes access rights and cannot be easily undone, particularly in the context of schema-level access…
Attacks that exploit this kind of access
Revoke schema privileges from a role. It is categorised as a Destructive tool in the Database MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Database MCP Server MCP server in PolicyLayer and add a rule for db_revoke_schema: 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 Database MCP Server. Nothing to install.
db_revoke_schema 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 db_revoke_schema 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 db_revoke_schema. 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.
db_revoke_schema is provided by the Database MCP Server MCP server (roilanrodriguez55/database-mcp). 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 →