get_meet_ivods
AI agents call get_meet_ivods 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 video recordings of legislative meetings—a read-only operation with no side effects. No data is created, modified, deleted, or executed. The 'get_' prefix and context among other query tools confirms it is a data retrieval function. Even with empty description, the naming convention and sibling tool patterns strongly indicate a safe read operation.
From the tool's definition Tool name 'get_meet_ivods' indicates retrieval of IVOD (Internet Video on Demand) recordings from legislative meetings. The server description explicitly lists 'IVOD recordings' as data accessed through read-only query operations.
Attacks that exploit this kind of access
get_meet_ivods. 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_ivods: 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_ivods 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_ivods 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_ivods. 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_ivods 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 →