Get recent parliamentary events: votes/divisions, party rebellions, bill stage changes, or a specific MP
AI agents call get_events to retrieve information from UK Parliament MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries publicly available parliamentary data without side effects. It performs passive observation of voting records, legislative changes, and MP information. No data is created, modified, deleted, or executed. The information accessed is already public in UK Parliament records.
From the tool's definition Tool description states 'Get recent parliamentary events' and lists retrieval operations: 'votes/divisions, party rebellions, bill stage changes, or a specific MP'. The verb 'Get' indicates data retrieval with no modification or execution capability.
Documented attack patterns abuse exactly the kind of access get_events gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and UK Parliament MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_events:
{
"version": "1",
"default": "deny",
"tools": {
"get_events": {}
}
}get_events is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get recent parliamentary events: votes/divisions, party rebellions, bill stage changes, or a specific MP. It is categorised as a Read tool in the UK Parliament MCP Server MCP Server, which means it retrieves data without modifying state.
Register the UK Parliament MCP Server MCP server in PolicyLayer and add a rule for get_events: 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 UK Parliament MCP Server. Nothing to install.
get_events 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 get_events 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 get_events. 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.
get_events is provided by the UK Parliament MCP Server MCP server (kupad95/uk-parliament-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from UK Parliament MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 UK Parliament MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.