get_new_listings
AI agents call get_new_listings 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 retrieves new rental listings from boligportal.dk. It performs a read-only query operation with no side effects—it does not create, modify, delete, or execute external actions. The sibling tools (get_seen_stats, mark_seen, reset_seen, search_listings) further confirm a monitoring/tracking pattern where get_new_listings is a straightforward data retrieval function.
From the tool's definition Tool name 'get_new_listings' indicates retrieval of listing data. Server description states it 'provides tools to search, filter, and track apartment listings.' The empty description is uninformative, but the function name and server context strongly suggest…
Attacks that exploit this kind of access
get_new_listings. 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_new_listings: 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_new_listings 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_new_listings 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_new_listings. 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_new_listings 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 →