query_uk_planning
Planning applications from the official planning.data.gov.uk feed, normalized to one schema. Blind Mode: no applicant personal data. Filters combine with AND; q searches all text fields. Costs 1 credit(s) per call.
This record as markdown: /tools/com-gankdat-gankdat/query-uk-planning.md
What query_uk_planning does on Gankdat
AI agents call query_uk_planning to retrieve information from Gankdat 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 |
|---|---|---|---|
q | string | — | |
page | integer | — | |
per_page | integer | — | |
authority | number | — | |
reference | string | — | |
decision_date_after | string | — | |
decision_date_before | string | — |
Parameters from the server's own tool schema.
Why query_uk_planning is rated Low
This tool retrieves and searches publicly available planning application records. It has no side effects—it only queries and returns data. The 'Blind Mode: no applicant personal data' qualifier confirms it is read-only and stripped of sensitive identifiers. Misuse would be limited to information gathering; no destructive, financial, or code-execution risks exist.
From the tool's definition Tool performs queries on planning application data: 'Planning applications from the official planning.data.gov.uk feed, normalized to one schema.' The description uses filter and search language ('Filters combine with AND; q searches all text fields')…
Attacks that exploit this kind of access
The rule that runs query_uk_planning safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gankdat, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For query_uk_planning, this is the rule to start with:
query_uk_planning 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 Gankdat, apply this rule, and every query_uk_planning call is checked against it from then on.
Questions about query_uk_planning
Planning applications from the official planning.data.gov.uk feed, normalized to one schema. Blind Mode: no applicant personal data. Filters combine with AND; q searches all text fields. Costs 1 credit(s) per call. It is categorised as a Read tool in the Gankdat MCP Server, which means it retrieves data without modifying state.
query_uk_planning accepts 7 parameters: q, page, per_page, authority, reference, decision_date_after, decision_date_before. The full parameter table on this page comes from the server's own tool schema.
Register the Gankdat MCP server in PolicyLayer and add a rule for query_uk_planning: 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 Gankdat. Nothing to install.
query_uk_planning 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 query_uk_planning 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 query_uk_planning. 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.
query_uk_planning is provided by the Gankdat MCP server (https://gankdat.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gankdat, and thousands of servers like it.
This server
Across the catalogue