Search parliamentary divisions (votes) by keyword.
AI agents call search_divisions to retrieve information from GovUK MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only search operation on public parliamentary voting records. No side effects, data modification, code execution, or destructive actions are possible. The severity is low because the data returned is already public and historical in nature, with no sensitive personal information exposure or operational impact from misuse.
From the tool's definition The tool name 'search_divisions' and description 'Search parliamentary divisions (votes) by keyword' indicate a query-only operation that retrieves historical voting data without modifying, executing, or destroying any data.
Attacks that exploit this kind of access
Search parliamentary divisions (votes) by keyword. It is categorised as a Read tool in the GovUK MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GovUK MCP Server MCP server in PolicyLayer and add a rule for search_divisions: 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 GovUK MCP Server. Nothing to install.
search_divisions 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 search_divisions 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 search_divisions. 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.
search_divisions is provided by the GovUK MCP Server MCP server (stealth-labs-ltd/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 →