neptime_clear_history

Clear all watch history. This action is IRREVERSIBLE. Returns: Confirmation of history cleared.

Server Neptime neptime-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What neptime_clear_history does on Neptime

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

Why neptime_clear_history needs a policy

This tool irreversibly deletes user data (complete watch history) without the ability to restore it. While not a direct financial or system-level impact, the permanent destruction of personal user records qualifies it as Destructive rather than Write. The irreversibility is explicitly called out in the description.

From the tool's definition Tool description explicitly states "This action is IRREVERSIBLE" and the operation is to "Clear all watch history" - a permanent deletion of user data with no undo capability.

Risk signalsBulk/mass operation — affects multiple targets

Questions about neptime_clear_history

What does the neptime_clear_history tool do? +

Clear all watch history. This action is IRREVERSIBLE. Returns: Confirmation of history cleared. It is categorised as a Destructive tool in the Neptime 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 neptime_clear_history? +

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

What risk level is neptime_clear_history? +

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

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

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

neptime_clear_history is provided by the Neptime MCP server (neptime-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.