get_mp_profile
A read tool on the UK Parliament MCP server.
This record as markdown: /tools/chrisbrooksbank-uk-parliament-mcp-lab/get-mp-profile.md
What get_mp_profile does on UK Parliament MCP Server
AI agents call get_mp_profile 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_mp_profile is rated Low
This tool retrieves profile data about Members of Parliament. UK Parliament data is public, and 'get' operations are fundamentally read operations with no side effects, data modification, execution capabilities, or financial implications. Low severity reflects that misuse would only expose publicly available information already accessible through parliament.uk.
From the tool's definition Tool name 'get_mp_profile' indicates retrieval of publicly available MP profile information. Sibling tools on this server (bill_stages, check_mp_vote, get_act_of_parliament, etc.) are all Read-category data retrieval operations consistent with a public…
Attacks that exploit this kind of access
The rule that runs get_mp_profile 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_mp_profile, this is the rule to start with:
get_mp_profile 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 get_mp_profile call is checked against it from then on.
Questions about get_mp_profile
get_mp_profile 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 get_mp_profile: 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.
get_mp_profile 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 get_mp_profile 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 get_mp_profile. 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.
get_mp_profile 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