get_parliamentary_diary
A read tool on the UK Parliament MCP server.
This record as markdown: /tools/chrisbrooksbank-uk-parliament-mcp-lab/get-parliamentary-diary.md
What get_parliamentary_diary does on UK Parliament MCP Server
AI agents call get_parliamentary_diary 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_parliamentary_diary is rated Low
A parliamentary diary lookup is a read operation that retrieves publicly available scheduling information. No description provided, but the naming pattern and contextual tools indicate this queries parliamentary calendars or event schedules without modification capabilities. Risk is minimal as it accesses public information with no side effects.
From the tool's definition Tool name 'get_parliamentary_diary' suggests retrieval of parliamentary scheduling/diary data. Sibling tools (bill_stages, browse_erskine_may_index, check_mp_vote, get_act_of_parliament, get_all_bills_rss, etc.) are all read-only query operations returning…
Attacks that exploit this kind of access
The rule that runs get_parliamentary_diary 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_parliamentary_diary, this is the rule to start with:
get_parliamentary_diary 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_parliamentary_diary call is checked against it from then on.
Questions about get_parliamentary_diary
get_parliamentary_diary 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 get_parliamentary_diary: 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_parliamentary_diary 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_parliamentary_diary 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_parliamentary_diary. 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_parliamentary_diary 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