get_session_by_id
A read tool on the UK Parliament MCP server.
This record as markdown: /tools/chrisbrooksbank-uk-parliament-mcp-lab/get-session-by-id.md
What get_session_by_id does on UK Parliament MCP Server
AI agents call get_session_by_id 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_session_by_id is rated Low
The tool appears to retrieve a parliamentary session record by ID, consistent with the server's purpose of querying UK Parliament data. No modification, deletion, execution, or financial operations are implied. The lack of description lowers confidence slightly, but the clear naming convention and analogous sibling tools support classification as a Read operation with low severity.
From the tool's definition Tool name 'get_session_by_id' indicates retrieval of data by identifier. Context shows sibling tools like 'get_amendment_by_id' and 'get_act_of_parliament' which are clearly read-only queries of UK Parliament data.
Attacks that exploit this kind of access
The rule that runs get_session_by_id 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_session_by_id, this is the rule to start with:
get_session_by_id 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_session_by_id call is checked against it from then on.
Questions about get_session_by_id
get_session_by_id 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_session_by_id: 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_session_by_id 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_session_by_id 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_session_by_id. 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_session_by_id 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