get_historic_sitting_day

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-historic-sitting-day.md

What get_historic_sitting_day does on UK Parliament MCP Server

AI agents call get_historic_sitting_day 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_historic_sitting_day is rated Low

The tool appears to retrieve historical parliamentary sitting day data without modifying, executing, or deleting anything. The context of other Read-category tools on this server (get_*, browse_*, check_*) combined with the 'get_' prefix strongly indicates a read-only query operation. Confidence is slightly reduced due to empty description, but the naming convention is clear.

From the tool's definition Tool name 'get_historic_sitting_day' indicates retrieval of historical parliamentary sitting day information.

Questions about get_historic_sitting_day

What does the get_historic_sitting_day tool do? +

get_historic_sitting_day 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_historic_sitting_day? +

Register the UK Parliament MCP Server MCP server in PolicyLayer and add a rule for get_historic_sitting_day: 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_historic_sitting_day? +

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

Can I rate-limit get_historic_sitting_day? +

Yes. Add a rate_limit block to the get_historic_sitting_day 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_historic_sitting_day completely? +

Set action: deny in the PolicyLayer policy for get_historic_sitting_day. 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_historic_sitting_day? +

get_historic_sitting_day 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of UK Parliament MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.