get_committee_publications_summary

What get_committee_publications_summary does on UK Parliament MCP Server

AI agents call get_committee_publications_summary 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_committee_publications_summary is rated Low

The tool name strongly suggests data retrieval ('get') of committee publication summaries from UK Parliament data. No indication of modification, deletion, execution, or financial operations. The naming convention aligns with other read-only tools in the server. Empty description slightly reduces confidence, but the name itself is sufficiently descriptive to classify this as a Read operation with low severity.

From the tool's definition Tool name 'get_committee_publications_summary' contains the verb 'get', which indicates retrieval of data. The sibling tools (bill_stages, browse_erskine_may_index, check_mp_vote, get_act_of_parliament, etc.) all follow read-only query patterns.

The rule that runs get_committee_publications_summary 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_committee_publications_summary, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_committee_publications_summary": {}
  }
}

Questions about get_committee_publications_summary