remove_dataset_logs

Remove one or more logs from a dataset by filter. To delete a single log, pass filter { unique_id: { operator:

Server Respan MCP Server respanai/respan-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What remove_dataset_logs does on Respan MCP Server

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

Why remove_dataset_logs needs a policy

This tool deletes or removes log entries from a dataset, which cannot be undone. Deletion of monitoring and audit logs is a destructive action with potentially significant impact on data integrity, compliance, and system observability. An AI agent misusing this tool could eliminate critical operational records. This is classified as Destructive rather than Write because the action is irreversible.

From the tool's definition Tool name 'remove_dataset_logs' and description 'Remove one or more logs from a dataset by filter' indicate irreversible deletion of log data. The verb 'remove' in the context of log management constitutes destructive action.

Questions about remove_dataset_logs

What does the remove_dataset_logs tool do? +

Remove one or more logs from a dataset by filter. To delete a single log, pass filter { unique_id: { operator:. It is categorised as a Destructive tool in the Respan MCP Server 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 remove_dataset_logs? +

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

What risk level is remove_dataset_logs? +

remove_dataset_logs 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 remove_dataset_logs? +

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

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

remove_dataset_logs is provided by the Respan MCP Server MCP server (respanai/respan-mcp). 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.