reset_seen

Clear all seen-listing history. After this, all listings will appear as new.

Server BoligWatch MCP Server nille/boligwatch
Category Destructive
Risk class Critical
Parameters 00 required

What reset_seen does on BoligWatch MCP Server

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

Why reset_seen needs a policy

This tool permanently deletes user state data (the seen-listing history). While it doesn't affect external systems or financial data, it destroys application state irreversibly. A misuse by an AI agent could reset important tracking progress a user has maintained, requiring manual recovery. This severity exceeds Write (which is reversible modification) and fits Destructive criteria for irreversible deletion of data.

From the tool's definition The tool description explicitly states it will "Clear all seen-listing history" with the effect that "all listings will appear as new." This irreversibly destroys the user's tracking state and cannot be easily undone without manually rebuilding the history.

Risk signalsBulk/mass operation — affects multiple targets

Questions about reset_seen

What does the reset_seen tool do? +

Clear all seen-listing history. After this, all listings will appear as new. It is categorised as a Destructive tool in the BoligWatch 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 reset_seen? +

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

What risk level is reset_seen? +

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

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

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

reset_seen is provided by the BoligWatch MCP Server MCP server (nille/boligwatch). 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.