uk-landregistry-pricepaid.property.by_area

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 90 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/uk-landregistry-pricepaid.property.by-area.md

WHAT IT DOES

What uk-landregistry-pricepaid.property.by_area does on Apibase

AI agents call uk-landregistry-pricepaid.property.by_area to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`page`	integer	—	Zero-based page number for pagination (default 0).
`town`	string	—	Town/post town to search (e.g. "WARRINGTON"). At least one of town, county, district is required.
`county`	string	—	County to search (e.g. "GREATER LONDON"). At least one of town, county, district is required.
`district`	string	—	Local authority district to search (e.g. "WARRINGTON"). At least one of town, county, district is required.
`max_date`	object	—	Only include transactions completed on/before this date (YYYY-MM-DD).
`min_date`	string	—	Only include transactions completed on/after this date (YYYY-MM-DD).
`max_price`	number	—	Maximum price paid in GBP.
`min_price`	number	—	Minimum price paid in GBP.
`page_size`	integer	—	Number of transactions per page (1-100, default 20).

Parameters from the server's own tool schema.

RISK

Why uk-landregistry-pricepaid.property.by_area is rated Low

Retrieves historical property transaction data from public registry without modification or execution capabilities.

From the tool's definition Search HM Land Registry Price Paid Data by town, county, local authority district

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs uk-landregistry-pricepaid.property.by_area safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For uk-landregistry-pricepaid.property.by_area, this is the rule to start with:

uk-landregistry-pricepaid.property.by_area Allowed

uk-landregistry-pricepaid.property.by_area is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "uk-landregistry-pricepaid.property.by_area": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every uk-landregistry-pricepaid.property.by_area call is checked against it from then on.

FAQ

Questions about uk-landregistry-pricepaid.property.by_area

What does the uk-landregistry-pricepaid.property.by_area tool do? +

Search HM Land Registry Price Paid Data by town, county, and/or local authority district (at least one required) — e.g. town="WARRINGTON" or county="GREATER LONDON". Optional filters: min/max price paid (GBP), min/max transaction date (YYYY-MM-DD), and pagination. Returns the same per-sale fields as search_by_postcode. Data: HM Land Registry, no auth required, Open Government Licence v3.0. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does uk-landregistry-pricepaid.property.by_area accept? +

uk-landregistry-pricepaid.property.by_area accepts 9 parameters: page, town, county, district, max_date, min_date, max_price, min_price, page_size. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on uk-landregistry-pricepaid.property.by_area? +

Register the Apibase MCP server in PolicyLayer and add a rule for uk-landregistry-pricepaid.property.by_area: 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 Apibase. Nothing to install.

What risk level is uk-landregistry-pricepaid.property.by_area? +

uk-landregistry-pricepaid.property.by_area is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit uk-landregistry-pricepaid.property.by_area? +

Yes. Add a rate_limit block to the uk-landregistry-pricepaid.property.by_area 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.

How do I block uk-landregistry-pricepaid.property.by_area completely? +

Set action: deny in the PolicyLayer policy for uk-landregistry-pricepaid.property.by_area. 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.

What MCP server provides uk-landregistry-pricepaid.property.by_area? +

uk-landregistry-pricepaid.property.by_area is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →