取得立法院 API 的統計資訊。
AI agents call get_stat 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 statistical information from the Taiwan Legislative Yuan API. It is a read-only query operation that fetches pre-computed or aggregated statistics. There are no side effects, no data modifications, no code execution, and no destructive operations. The blast radius of misuse is minimal—an agent could retrieve unwanted statistics but cannot cause harm.
From the tool's definition Tool name 'get_stat' and description '取得立法院 API 的統計資訊' (retrieve statistics information from Legislative Yuan API) indicate this retrieves aggregate data or metrics without modifying any state.
Attacks that exploit this kind of access
取得立法院 API 的統計資訊。. 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_stat: 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_stat 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_stat 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_stat. 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_stat 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 →