List Knesset members (MKs) with party (faction) affiliation for a given Knesset. Uses PositionID=54 on KNS_PersonToPosition, which is the row that carries FactionID/FactionName (PositionID=43 exists but has null faction fields). Optionally filter by factionId — use list-factions to discover IDs. ...
AI agents call list-knesset-members to retrieve information from Knesset MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries publicly available information about Israeli Knesset members and their party affiliations. It has no side effects, cannot modify data, and poses minimal risk if misused by an AI agent — the worst outcome would be retrieving information that is already public. This clearly fits the Read category (search, list, get, fetch).
From the tool's definition Tool description explicitly states it "List[s] Knesset members" and "filter[s] by factionId". The function performs querying and retrieval of public parliamentary data with "Optionally filter" as the only parameter variation.
Attacks that exploit this kind of access
List Knesset members (MKs) with party (faction) affiliation for a given Knesset. Uses PositionID=54 on KNS_PersonToPosition, which is the row that carries FactionID/FactionName (PositionID=43 exists but has null faction fields). Optionally filter by factionId — use list-factions to discover IDs. Note: an MK who switched factions mid-term appears once per stint. It is categorised as a Read tool in the Knesset MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Knesset MCP Server MCP server in PolicyLayer and add a rule for list-knesset-members: 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 Knesset MCP Server. Nothing to install.
list-knesset-members 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 list-knesset-members 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 list-knesset-members. 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.
list-knesset-members is provided by the Knesset MCP Server MCP server (zohar/knesset-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →