search_calendar
A read tool on the UK Parliament MCP server.
This record as markdown: /tools/chrisbrooksbank-uk-parliament-mcp-lab/search-calendar.md
What search_calendar does on UK Parliament MCP Server
AI agents call search_calendar 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 search_calendar is rated Low
The name 'search_calendar' indicates a query operation. The server context (parliamentary data access for queries) and pattern of sibling tools strongly suggest this is a read-only search. The empty description reduces confidence slightly, but the overwhelming context points to a benign data retrieval function. Risk is minimal as parliamentary calendar data is public.
From the tool's definition Tool name is 'search_calendar' with empty description. Based on sibling tools (bill_stages, browse_erskine_may_index, check_mp_vote, get_act_of_parliament, get_amendment_by_id, get_all_bills_rss) which are all read-only queries of UK Parliament data, and the…
Attacks that exploit this kind of access
The rule that runs search_calendar 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 search_calendar, this is the rule to start with:
search_calendar 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 search_calendar call is checked against it from then on.
Questions about search_calendar
search_calendar 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.
Register the UK Parliament MCP Server MCP server in PolicyLayer and add a rule for search_calendar: 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.
search_calendar 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_calendar 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_calendar. 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_calendar 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