search_petitions
AI agents call search_petitions to retrieve information from Open Assembly without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'search_petitions' performs a read-only search operation on public legislative petition data. Despite the empty description, the server's purpose (querying bills, members, votes, committees) and all sibling tools being read-only retrieval operations confirm this is a Read operation with no side effects.
From the tool's definition Tool name 'search_petitions' indicates a query/search operation; context shows sibling tools are all read-only APIs (get_*, analyze_*, discover_*) for querying Korean National Assembly data; no description provided but naming convention and API context…
Attacks that exploit this kind of access
search_petitions. It is categorised as a Read tool in the Open Assembly MCP Server, which means it retrieves data without modifying state.
Register the Open Assembly MCP server in PolicyLayer and add a rule for search_petitions: 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 Open Assembly. Nothing to install.
search_petitions 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_petitions 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_petitions. 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_petitions is provided by the Open Assembly MCP server (kyusik-yang/open-assembly-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 →