get_event_by_id

A read tool on the UK Parliament MCP server.

SERVERUK Parliament MCP Server SOURCEchrisbrooksbank/uk-parliament-mcp-lab

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/chrisbrooksbank-uk-parliament-mcp-lab/get-event-by-id.md

WHAT IT DOES

What get_event_by_id does on UK Parliament MCP Server

AI agents call get_event_by_id to retrieve information from UK Parliament MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_event_by_id is rated Low

The 'get_' prefix combined with 'by_id' pattern is a standard retrieval operation that queries existing data without modification, deletion, or side effects. Within the UK Parliament domain, this would return parliamentary event details (debates, votes, committee meetings, etc.).

From the tool's definition Tool name 'get_event_by_id' suggests retrieval of a single event record by identifier. The broader server context (querying MPs, bills, votes, committees, debates) indicates read-only parliamentary data access.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_event_by_id safely

PolicyLayer is an MCP gateway: it sits between your AI agents and UK Parliament MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_event_by_id, this is the rule to start with:

get_event_by_id Allowed

get_event_by_id is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_event_by_id": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UK Parliament MCP Server, apply this rule, and every get_event_by_id call is checked against it from then on.

FAQ

Questions about get_event_by_id

What does the get_event_by_id tool do? +

get_event_by_id is a read tool on the UK Parliament MCP Server MCP server. It is categorised as a Read tool in the UK Parliament MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_event_by_id? +

Register the UK Parliament MCP Server MCP server in PolicyLayer and add a rule for get_event_by_id: 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.

What risk level is get_event_by_id? +

get_event_by_id is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_event_by_id? +

Yes. Add a rate_limit block to the get_event_by_id 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.

How do I block get_event_by_id completely? +

Set action: deny in the PolicyLayer policy for get_event_by_id. 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.

What MCP server provides get_event_by_id? +

get_event_by_id is provided by the UK Parliament MCP Server MCP server (chrisbrooksbank/uk-parliament-mcp-lab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UK Parliament MCP Server, and thousands of servers like it.

This server

All 209 UK Parliament MCP Server tools →

Across the catalogue

get_event_details on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →