Get statistics about the seen-listings tracker.
AI agents call get_seen_stats to retrieve information from BoligWatch MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and returns statistical information about listings that have been marked as seen. It performs no side effects, does not modify data, does not execute external operations, and does not involve financial transactions. It is a straightforward read operation with minimal security risk.
From the tool's definition Tool name 'get_seen_stats' and description 'Get statistics about the seen-listings tracker' indicate a retrieval operation that queries tracker statistics without modifying data.
Attacks that exploit this kind of access
Get statistics about the seen-listings tracker. It is categorised as a Read tool in the BoligWatch MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BoligWatch MCP Server MCP server in PolicyLayer and add a rule for get_seen_stats: 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.
get_seen_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_seen_stats 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.
Set action: deny in the PolicyLayer policy for get_seen_stats. 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.
get_seen_stats 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.
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 →