get_commons_voting_record_for_member

What get_commons_voting_record_for_member does on UK Parliament MCP Server

AI agents call get_commons_voting_record_for_member 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_commons_voting_record_for_member is rated Low

This tool retrieves voting records for a specific MP in the House of Commons—a read-only query operation with no side effects. No data is created, modified, deleted, or financially committed. The blast radius of misuse is minimal since it only exposes already-public parliamentary voting data. The empty description prevents full certainty, but the method name and server context strongly indicate a Read classification.

From the tool's definition Tool name 'get_commons_voting_record_for_member' indicates retrieval of historical voting data. Sibling tools like 'check_mp_vote', 'get_amendment_by_id', and 'get_act_of_parliament' are all Read operations that query Parliament data.

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

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

Questions about get_commons_voting_record_for_member