get_bill_detail
AI agents call get_bill_detail 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 and server context indicate this tool retrieves detailed legislative bill information without modifying, executing, or deleting data. This is a read-only query operation typical of a legislative data API. Confidence is not higher due to empty description, but the consistent naming pattern and sibling tools all being queries makes classification as Read appropriate.
From the tool's definition Tool name 'get_bill_detail' follows the get_* naming pattern consistent with sibling tools like get_bill_summary, get_member_info, and get_member_votes. Server description indicates these tools enable 'querying' of legislative data.
Attacks that exploit this kind of access
get_bill_detail. 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 get_bill_detail: 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.
get_bill_detail 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 get_bill_detail 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 get_bill_detail. 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.
get_bill_detail 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 →