Get listings associated with a specific agent by agent ID.
AI agents call getListingsByAgent 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 data (listings) filtered by a parameter (agent ID) without modifying, creating, or deleting any records. It is a straightforward query operation that returns existing data. The blast radius of misuse is minimal—an agent could retrieve listing data it shouldn't see, but cannot alter or destroy anything. This is categorized as Read with low severity.
From the tool's definition Tool description explicitly states 'Get listings' - a retrieval operation with no modification, creation, or deletion. The verb 'Get' and the read-only nature of querying listings by agent ID indicate no side effects.
Attacks that exploit this kind of access
Get listings associated with a specific agent by agent ID. 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 getListingsByAgent: 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.
getListingsByAgent 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 getListingsByAgent 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 getListingsByAgent. 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.
getListingsByAgent 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 →