mark_seen · BoligWatch MCP Server MCP: Risk & Policy

WHAT IT DOES

What mark_seen does on BoligWatch MCP Server

AI agents use mark_seen to create or update resources in BoligWatch MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BoligWatch MCP Server environment.

WHY IT NEEDS A POLICY

Why mark_seen needs a policy

This tool creates or modifies data reversibly—it changes the internal state of which listings have been marked as seen. This is a state-tracking modification without side effects on external systems or irreversible consequences. The action can be undone (listings can be unmarked or reset via the sibling tool reset_seen).

From the tool's definition Tool description: 'Mark specific listing IDs as seen so they won't appear in get_new_listings.' This modifies the state of listings by changing their 'seen' status.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mark_seen Rate-limited

mark_seen stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mark_seen": {
      "limits": [
        {
          "counter": "mark_seen_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches BoligWatch MCP Server, so you can run agents against it safely.

FAQ

Questions about mark_seen

What does the mark_seen tool do? +

Mark specific listing IDs as seen so they won't appear in get_new_listings. It is categorised as a Write tool in the BoligWatch MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mark_seen? +

Register the BoligWatch MCP Server MCP server in PolicyLayer and add a rule for mark_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 mark_seen? +

mark_seen is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mark_seen? +

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

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

mark_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.

// THE FULL RECORD

mark_seen is one line of BoligWatch MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →