AI agents call count-properties to retrieve information from Real Estate Data MCP Server by BatchData without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though count-properties only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Documented attack patterns abuse exactly the kind of access count-properties gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Real Estate Data MCP Server by BatchData, and nothing reaches the server without passing your rules. This is the rule we recommend for count-properties:
{
"version": "1",
"default": "deny",
"tools": {
"count-properties": {}
}
}count-properties is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
count-properties. It is categorised as a Read tool in the Real Estate Data MCP Server by BatchData MCP Server, which means it retrieves data without modifying state.
Register the Real Estate Data MCP Server by BatchData MCP server in PolicyLayer and add a rule for count-properties: 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 Real Estate Data MCP Server by BatchData. Nothing to install.
count-properties 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 count-properties 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 count-properties. 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.
count-properties is provided by the Real Estate Data MCP Server by BatchData MCP server (zellerhaus/batchdata-mcp-real-estate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Real Estate Data MCP Server by BatchData tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Real Estate Data MCP Server by BatchData tools catalogued and risk-classified — across an index of 42,500+ MCP servers.