국회 회의록을 검색합니다. 본회의, 위원회 회의록을 키워드, 날짜, 위원회별로 검색할 수 있습니다.
AI agents call search_meeting_records to retrieve information from Korean National Assembly 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 and queries existing legislative meeting records—a classic Read operation with no side effects. The blast radius of misuse is minimal; an AI agent could only access historical legislative data that is already public. No data modification, deletion, code execution, or financial impact is possible.
From the tool's definition Tool description indicates it searches (검색합니다) meeting records (회의록) from the National Assembly by keyword, date, and committee.
Attacks that exploit this kind of access
국회 회의록을 검색합니다. 본회의, 위원회 회의록을 키워드, 날짜, 위원회별로 검색할 수 있습니다. It is categorised as a Read tool in the Korean National Assembly MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Korean National Assembly MCP Server MCP server in PolicyLayer and add a rule for search_meeting_records: 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 Korean National Assembly MCP Server. Nothing to install.
search_meeting_records 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 search_meeting_records 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 search_meeting_records. 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.
search_meeting_records is provided by the Korean National Assembly MCP Server MCP server (hollobit/assembly-api-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 →