query_assembly
AI agents call query_assembly 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 server's stated purpose is querying legislative data via natural language, and all named sibling tools are read operations (get_*, analyze_*). Although the description is empty, the context strongly indicates 'query_assembly' retrieves rather than modifies legislative records. Confidence is moderately high but reduced due to the empty description.
From the tool's definition Tool name is 'query_assembly' with an empty description. Based on sibling tools like 'get_bill_detail', 'get_member_info', 'get_member_votes', 'get_committee_members', and the server's purpose to enable 'querying of bills, members, votes, committees', the…
Attacks that exploit this kind of access
query_assembly. 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 query_assembly: 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.
query_assembly 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_assembly 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_assembly. 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_assembly 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 →