uk-landregistry-pricepaid.property.transaction
Get a single HM Land Registry price-paid transaction by its GUID transaction_id. Returns price paid, transaction date, property type, estate type, new-build flag, and full address. Call search_by_postcode or search_by_area first to find a transaction_id. Data: HM Land Registry, no auth required, ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/uk-landregistry-pricepaid.property.transaction.md
What uk-landregistry-pricepaid.property.transaction does on Apibase
AI agents call uk-landregistry-pricepaid.property.transaction 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 |
|---|---|---|---|
transaction_id | string | Yes | HM Land Registry transaction GUID (e.g. "702EF0D1-AB60-4A1B-A2A1-C127E1EDE547"). Obtain from search_by_postcode or search_by_area. |
Parameters from the server's own tool schema.
Why uk-landregistry-pricepaid.property.transaction is rated Low
Retrieves read-only public property transaction data with no side effects.
From the tool's definition Get a single HM Land Registry price-paid transaction by GUID
Attacks that exploit this kind of access
The rule that runs uk-landregistry-pricepaid.property.transaction 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.transaction, this is the rule to start with:
uk-landregistry-pricepaid.property.transaction is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every uk-landregistry-pricepaid.property.transaction call is checked against it from then on.
Questions about uk-landregistry-pricepaid.property.transaction
Get a single HM Land Registry price-paid transaction by its GUID transaction_id. Returns price paid, transaction date, property type, estate type, new-build flag, and full address. Call search_by_postcode or search_by_area first to find a transaction_id. 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.
uk-landregistry-pricepaid.property.transaction accepts 1 parameter: transaction_id. Required: transaction_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for uk-landregistry-pricepaid.property.transaction: 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.
uk-landregistry-pricepaid.property.transaction 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 uk-landregistry-pricepaid.property.transaction 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 uk-landregistry-pricepaid.property.transaction. 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.
uk-landregistry-pricepaid.property.transaction 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.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue