Get published listings for a site, with optional pagination.
AI agents call getPublishedListings to retrieve information from Lofty 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 published listing data from a CRM system. The verb 'Get' combined with pagination parameters confirms it is a read-only query operation. There is no evidence of data creation, modification, deletion, code execution, or financial transactions. The blast radius of misuse is minimal—an agent could access listings it shouldn't, but cannot alter data or trigger external operations.
From the tool's definition Tool name 'getPublishedListings' and description 'Get published listings for a site, with optional pagination' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get published listings for a site, with optional pagination. It is categorised as a Read tool in the Lofty MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lofty MCP Server MCP server in PolicyLayer and add a rule for getPublishedListings: 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 Lofty MCP Server. Nothing to install.
getPublishedListings 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 getPublishedListings 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 getPublishedListings. 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.
getPublishedListings is provided by the Lofty MCP Server MCP server (nerdsnipe-inc/lofty-mcp). 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 →