delete_data_row

Delete a workspace data row. IMMEDIATE — there is no archive / undo. Use with care.

Server Hubnote Mcp wlzerd/hubnote-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_data_row does on Hubnote Mcp

AI agents call delete_data_row to permanently remove resources in Hubnote Mcp — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_data_row needs a policy

This tool permanently deletes data without recovery options. It matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The severity is high because data loss in a workspace management system could affect multiple users and workflows, though the blast radius is somewhat limited to individual data rows rather than entire systems.

From the tool's definition Tool description explicitly states: 'Delete a workspace data row. IMMEDIATE — there is no archive / undo.' The use of capital 'IMMEDIATE' and explicit warning about lack of undo mechanism clearly indicates irreversible deletion.

Questions about delete_data_row

What does the delete_data_row tool do? +

Delete a workspace data row. IMMEDIATE — there is no archive / undo. Use with care. It is categorised as a Destructive tool in the Hubnote Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_data_row? +

Register the Hubnote MCP server in PolicyLayer and add a rule for delete_data_row: 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 Hubnote Mcp. Nothing to install.

What risk level is delete_data_row? +

delete_data_row is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_data_row? +

Yes. Add a rate_limit block to the delete_data_row 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.

How do I block delete_data_row completely? +

Set action: deny in the PolicyLayer policy for delete_data_row. 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.

What MCP server provides delete_data_row? +

delete_data_row is provided by the Hubnote MCP server (wlzerd/hubnote-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.