Get random property records. Returns a list of random property records.
AI agents call get_random_property_records to retrieve information from RentCast 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 and returns property records without creating, modifying, deleting, or executing any operations. The 'get_' prefix and passive 'returns' language confirm it is a read operation. The context of a property valuation/market data API (RentCast) further supports that this is informational data retrieval.
From the tool's definition Tool name 'get_random_property_records' and description 'Returns a list of random property records' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get random property records. Returns a list of random property records. It is categorised as a Read tool in the RentCast MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RentCast MCP Server MCP server in PolicyLayer and add a rule for get_random_property_records: 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 RentCast MCP Server. Nothing to install.
get_random_property_records 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_random_property_records 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_random_property_records. 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_random_property_records is provided by the RentCast MCP Server MCP server (robcerda/rentcast-mcp-server). 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 →