NYC tax-lot lookup via PLUTO — every NYC lot with owner, zoning, lot/building area, year built, classification, lat/lon. Pass bbl (10-digit Borough-Block-Lot) for exact lookup or address (partial) optionally constrained by borough (MN/BX/BK/QN/SI). The BBL returned here is the universal join key ...
AI agents call property.nyc-parcel-lookup to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval tool providing read-only access to NYC property tax records (PLUTO database). The 'lookup' and 'join key' language confirms query-based information retrieval. No financial transactions, code execution, or data modification occurs. While property information can be sensitive, the tool itself performs only non-destructive read operations.
From the tool's definition Tool description explicitly states it performs 'lookup' and 'retrieves' property data (owner, zoning, lot/building area, year built, classification, lat/lon, BBL). No modification, deletion, or execution capabilities are described.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
NYC tax-lot lookup via PLUTO — every NYC lot with owner, zoning, lot/building area, year built, classification, lat/lon. Pass bbl (10-digit Borough-Block-Lot) for exact lookup or address (partial) optionally constrained by borough (MN/BX/BK/QN/SI). The BBL returned here is the universal join key for property.nyc-deed-history / nyc-permits / nyc-violations. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for property.nyc-parcel-lookup: 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 Mcp. Nothing to install.
property.nyc-parcel-lookup 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 property.nyc-parcel-lookup 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 property.nyc-parcel-lookup. 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.
property.nyc-parcel-lookup is provided by the MCP server (@2sio/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 →