delete_matrix_rows

Delete rows from Knowledge Matrix with confirmation requirement. First call shows preview, second call with confirm=true executes deletion. Cannot delete header rows (1-2).

Server Revenue Engine MCP promptishoperations/mcpspec
Category Destructive
Risk class Critical
Parameters 00 required

What delete_matrix_rows does on Revenue Engine MCP

AI agents call delete_matrix_rows to permanently remove resources in Revenue Engine MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_matrix_rows needs a policy

This tool permanently removes data rows from a structured knowledge management system. Although it includes a safety mechanism (two-step confirmation with preview), the core action is irreversible deletion of data. This qualifies as Destructive rather than Write because the operation cannot be undone.

From the tool's definition Tool name 'delete_matrix_rows' and description explicitly states it 'Delete rows from Knowledge Matrix'. Deletion is irreversible data destruction.

Questions about delete_matrix_rows

What does the delete_matrix_rows tool do? +

Delete rows from Knowledge Matrix with confirmation requirement. First call shows preview, second call with confirm=true executes deletion. Cannot delete header rows (1-2). It is categorised as a Destructive tool in the Revenue Engine 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_matrix_rows? +

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

What risk level is delete_matrix_rows? +

delete_matrix_rows 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_matrix_rows? +

Yes. Add a rate_limit block to the delete_matrix_rows 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_matrix_rows completely? +

Set action: deny in the PolicyLayer policy for delete_matrix_rows. 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_matrix_rows? +

delete_matrix_rows is provided by the Revenue Engine MCP server (promptishoperations/mcpspec). 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.