search_committee_debates
A read tool on the UK Parliament MCP server.
This record as markdown: /tools/chrisbrooksbank-uk-parliament-mcp-lab/search-committee-debates.md
What search_committee_debates does on UK Parliament MCP Server
AI agents call search_committee_debates 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_committee_debates is rated Low
The 'search' prefix and committee debates context indicate this is a data retrieval function that queries Parliament records. No description is provided, but the naming pattern and sibling tools strongly suggest it retrieves debate information without side effects. Confidence is moderately high due to clear naming convention, though slightly reduced by the empty description.
From the tool's definition Tool name is 'search_committee_debates' with 'search' indicating data retrieval. Sibling tools in this server (bill_stages, browse_erskine_may_index, check_mp_vote, get_act_of_parliament) are all clearly Read operations that query Parliament data.
Attacks that exploit this kind of access
The rule that runs search_committee_debates 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_committee_debates, this is the rule to start with:
search_committee_debates 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_committee_debates call is checked against it from then on.
Questions about search_committee_debates
search_committee_debates 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_committee_debates: 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_committee_debates 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_committee_debates 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_committee_debates. 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_committee_debates 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