query_uk_tenders
Public procurement notices from the official Find a Tender OCDS feed, flattened to one queryable schema. Blind Mode: no contact or 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-tenders.md
What query_uk_tenders does on Gankdat
AI agents call query_uk_tenders 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 | — | |
buyer | string | — | |
status | string | — | |
per_page | integer | — | |
cpv_codes | string | — | |
value_amount_max | number | — | |
value_amount_min | number | — | |
procurement_method | string | — | |
published_at_after | string | — | |
published_at_before | string | — |
Parameters from the server's own tool schema.
Why query_uk_tenders is rated Low
This is a retrieval/search tool that queries a read-only public dataset. The 'query_*' naming convention combined with the description indicating filtering and searching without side effects, data modification, or destructive operations places it squarely in the Read category. The tool merely returns information from an existing public source.
From the tool's definition Tool performs queries against public procurement notices ("query", "queryable schema", "searches all text fields"); explicitly states "no contact or personal data" and operates on "Public procurement notices from the official Find a Tender OCDS feed." No…
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs query_uk_tenders 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_tenders, this is the rule to start with:
query_uk_tenders 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_tenders call is checked against it from then on.
Questions about query_uk_tenders
Public procurement notices from the official Find a Tender OCDS feed, flattened to one queryable schema. Blind Mode: no contact or 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_tenders accepts 11 parameters: q, page, buyer, status, per_page, cpv_codes, value_amount_max, value_amount_min, procurement_method, published_at_after, published_at_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_tenders: 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_tenders 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_tenders 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_tenders. 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_tenders 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