Delete user profile by user_id Removes the user profile from storage. This does not delete the user's memories, only the extracted profile information. Args: user_id: User identifier (required) Returns: JSON formatted string with success status
AI agents call delete_user_profile to permanently remove resources in Mcp Oceanbase — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes user profile data from storage. Deletion operations are irreversible and represent a destructive action that cannot be undone. While the blast radius is somewhat limited to one user's profile information (rather than entire databases), the permanence of the deletion and the potential loss of user data warrants high severity.
From the tool's definition Tool name is 'delete_user_profile' and description states 'Removes the user profile from storage' and 'Delete user profile by user_id'. The action is irreversible deletion of data.
Documented attack patterns abuse exactly the kind of access delete_user_profile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Oceanbase, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_user_profile:
{
"version": "1",
"default": "deny",
"hide": [
"delete_user_profile"
]
}delete_user_profile disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete user profile by user_id Removes the user profile from storage. This does not delete the user's memories, only the extracted profile information. Args: user_id: User identifier (required) Returns: JSON formatted string with success status. It is categorised as a Destructive tool in the Mcp Oceanbase MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Oceanbase MCP server in PolicyLayer and add a rule for delete_user_profile: 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 Mcp Oceanbase. Nothing to install.
delete_user_profile 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 delete_user_profile 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 delete_user_profile. 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.
delete_user_profile is provided by the Mcp Oceanbase MCP server (oceanbase/awesome-oceanbase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 134 Mcp Oceanbase tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
134 Mcp Oceanbase tools catalogued and risk-classified — across an index of 42,500+ MCP servers.