get_bill_doc_html
AI agents call get_bill_doc_html to retrieve information from Taiwan Legislative Yuan MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches and returns legislative bill documentation—a read-only operation with no side effects. Even though the description is empty, the naming convention and context of sibling read-only tools on a public legislative data API strongly indicate data retrieval. There is no capability to create, modify, delete, or execute operations.
From the tool's definition Tool name 'get_bill_doc_html' indicates retrieval of bill documentation in HTML format. Sibling tools (get_bill, get_committee, get_gazette, get_interpellation, get_ivod) are all read-only queries from the Legislative Yuan API v2.
Attacks that exploit this kind of access
get_bill_doc_html. It is categorised as a Read tool in the Taiwan Legislative Yuan MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Taiwan Legislative Yuan MCP Server MCP server in PolicyLayer and add a rule for get_bill_doc_html: 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 Taiwan Legislative Yuan MCP Server. Nothing to install.
get_bill_doc_html 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_doc_html 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_doc_html. 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_doc_html is provided by the Taiwan Legislative Yuan MCP Server MCP server (narumiruna/ly-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 →