check_mp_vote

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/check-mp-vote.md

WHAT IT DOES

What check_mp_vote does on UK Parliament MCP Server

AI agents call check_mp_vote 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.

RISK

Why check_mp_vote is rated Low

The tool appears to retrieve historical voting information about MPs—a query operation with no side effects. The empty description reduces confidence slightly, but the naming pattern (check_*) and server purpose (data access for AI assistants) strongly suggest read-only behavior. No evidence of write, execute, or destructive operations. Low severity due to the public nature of parliamentary voting records.

From the tool's definition Tool name 'check_mp_vote' indicates retrieval of voting records for Members of Parliament. The server context describes querying parliamentary data including 'votes' with no modification capability mentioned.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

check_mp_vote Allowed

check_mp_vote is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UK Parliament MCP Server, apply this rule, and every check_mp_vote call is checked against it from then on.

FAQ

Questions about check_mp_vote

What does the check_mp_vote tool do? +

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

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

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

Can I rate-limit check_mp_vote? +

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

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

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

KEEP EXPLORING

More on UK Parliament MCP Server, and thousands of servers like it.

This server

All 209 UK Parliament MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →