search_historic_sitting_days

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/search-historic-sitting-days.md

What search_historic_sitting_days does on UK Parliament MCP Server

AI agents call search_historic_sitting_days 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_historic_sitting_days is rated Low

The tool name contains 'search' which is inherently a Read operation that retrieves historical data about when Parliament was in session. There is no indication it modifies, deletes, or executes anything. The empty description lowers confidence slightly, but the naming convention and server context strongly suggest this is a data query tool.

From the tool's definition Tool name 'search_historic_sitting_days' indicates a search/query operation on parliamentary sitting day records.

Questions about search_historic_sitting_days

What does the search_historic_sitting_days tool do? +

search_historic_sitting_days 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 search_historic_sitting_days? +

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

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

Can I rate-limit search_historic_sitting_days? +

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

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

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