取得特定會議的詳細資訊。
AI agents call get_meet 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 or queries detailed information about legislative meetings from Taiwan's Legislative Yuan database. It has no side effects, does not modify data, execute commands, or delete anything. It is a straightforward read-only data retrieval operation, consistent with other sibling tools like get_bill, get_committee, and get_gazette which are all read operations against a public legislative database.
From the tool's definition Tool name 'get_meet' with description '取得特定會議的詳細資訊' (get details of a specific meeting). The verb 'get' and the function of retrieving meeting information indicates a retrieval operation with no modification or execution capabilities.
Attacks that exploit this kind of access
取得特定會議的詳細資訊。. 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_meet: 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_meet 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_meet 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_meet. 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_meet 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 →