Cross-dataset query: find MPs matching multiple conditions spanning vote records AND financial interests. Examples:
AI agents call query_entities to retrieve information from UK Parliament MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool searches and filters publicly available parliamentary data across multiple datasets (votes, financial interests) to retrieve matching MPs. No data is created, modified, deleted, or executed. While sensitive data (voting patterns, financial interests) may be accessible, the tool itself performs only read operations with no side effects.
From the tool's definition Tool performs a 'Cross-dataset query: find MPs matching multiple conditions spanning vote records AND financial interests.' This is a search/retrieval operation with no modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access query_entities gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and UK Parliament MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query_entities:
{
"version": "1",
"default": "deny",
"tools": {
"query_entities": {}
}
}query_entities is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Cross-dataset query: find MPs matching multiple conditions spanning vote records AND financial interests. Examples:. 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 query_entities: 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.
query_entities 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 query_entities 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 query_entities. 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.
query_entities is provided by the UK Parliament MCP Server MCP server (kupad95/uk-parliament-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from UK Parliament MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 UK Parliament MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.