get_calendar_event
Get calendar event by ID | specific event, event details | Use to get full details of a specific calendar event | Returns event details
This record as markdown: /tools/chrisbrooksbank-uk-parliament-mcp-lab/get-calendar-event.md
What get_calendar_event does on UK Parliament MCP Server
AI agents call get_calendar_event 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.
Why get_calendar_event is rated Low
This tool retrieves parliamentary calendar event information by ID and returns event details. It performs a query operation with no side effects, no data modification, no code execution, and no destructive actions. The low severity reflects that accessing public parliamentary calendar data poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_calendar_event' and description 'Get calendar event by ID | specific event, event details | Use to get full details of a specific calendar event | Returns event details' indicates retrieval of existing data with no modification, deletion, or…
Attacks that exploit this kind of access
The rule that runs get_calendar_event 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_calendar_event, this is the rule to start with:
get_calendar_event 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 UK Parliament MCP Server, apply this rule, and every get_calendar_event call is checked against it from then on.
Questions about get_calendar_event
Get calendar event by ID | specific event, event details | Use to get full details of a specific calendar event | Returns event details. 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_calendar_event: 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_calendar_event 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_calendar_event 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_calendar_event. 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_calendar_event 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.
More on UK Parliament MCP Server, and thousands of servers like it.
This server
Across the catalogue