Search bills by keyword in their name. Returns up to 20 most recent Knesset matches.
AI agents call search-bills-by-name 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 queries parliamentary data (bills) by keyword and returns results without creating, modifying, or deleting any data. It has no side effects or ability to trigger external operations. The return of up to 20 results represents a bounded, non-destructive read operation typical of search/query functionality.
From the tool's definition Tool performs a search operation that 'returns' bills matching keywords - a pure retrieval function with no modification, deletion, or execution capabilities. Description uses passive retrieval language ('returns').
Attacks that exploit this kind of access
Search bills by keyword in their name. Returns up to 20 most recent Knesset matches. 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 search-bills-by-name: 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.
search-bills-by-name 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 search-bills-by-name 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 search-bills-by-name. 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.
search-bills-by-name 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 →