get_committee_meets
AI agents call get_committee_meets 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 retrieves committee meeting data from Taiwan's Legislative Yuan public records. It has no write, delete, execute, or financial capabilities. The 'get_*' naming convention across all sibling tools and the read-only nature of legislative data access indicate this is a simple data query with no side effects.
From the tool's definition Tool name 'get_committee_meets' indicates retrieval of committee meeting information. The server provides 'comprehensive access' to 'meeting records' as stated in the server description.
Attacks that exploit this kind of access
get_committee_meets. 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_committee_meets: 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_committee_meets 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_committee_meets 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_committee_meets. 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_committee_meets 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 →