govuk_get_section
AI agents call govuk_get_section to retrieve information from GOV UK Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to retrieve a specific section from GOV.UK content based on the 'get' verb and sibling tools performing similar read operations. No write, execute, destructive, or financial capabilities are evident. Confidence is moderate (0.7) due to missing tool description; if the description had been provided, confidence would be higher.
From the tool's definition Tool name 'govuk_get_section' with pattern consistent with sibling tools (govuk_get_content, govuk_get_organisation) that are retrieval operations. Server description emphasizes 'search, content retrieval' as core functions.
Attacks that exploit this kind of access
govuk_get_section. It is categorised as a Read tool in the GOV UK Search MCP Server, which means it retrieves data without modifying state.
Register the GOV UK Search MCP server in PolicyLayer and add a rule for govuk_get_section: 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 GOV UK Search. Nothing to install.
govuk_get_section 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 govuk_get_section 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 govuk_get_section. 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.
govuk_get_section is provided by the GOV UK Search MCP server (paulieb89/govuk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →