browse_locations

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/browse-locations.md

WHAT IT DOES

What browse_locations does on UK Parliament MCP Server

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

The name 'browse_locations' implies a read/list operation for location data within the UK Parliament context (e.g., committee rooms, debate venues). No description is provided to confirm side effects, but 'browse' strongly implies a read-only retrieval operation. Confidence is lowered due to the empty description.

From the tool's definition Tool name 'browse_locations' suggests browsing/listing location data; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

browse_locations Allowed

browse_locations 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": {
    "browse_locations": {}
  }
}

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 browse_locations call is checked against it from then on.

FAQ

Questions about browse_locations

What does the browse_locations tool do? +

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

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

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

Can I rate-limit browse_locations? +

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

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

browse_locations 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 →