get_schedule
AI agents call get_schedule to retrieve information from Open Assembly without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name ('get_') and the consistent pattern of sibling tools that query Korean National Assembly data, this tool most likely retrieves schedule information (such as legislative or committee schedules) without side effects. The empty description lowers confidence slightly, but the naming convention and server context provide reasonable grounds for Read classification.
From the tool's definition Tool named 'get_schedule' with empty description; naming convention suggests data retrieval. Sibling tools on this server (get_bill_detail, get_member_info, get_member_votes, get_committee_members) are all Read operations that query legislative data without…
Attacks that exploit this kind of access
get_schedule. It is categorised as a Read tool in the Open Assembly MCP Server, which means it retrieves data without modifying state.
Register the Open Assembly MCP server in PolicyLayer and add a rule for get_schedule: 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 Open Assembly. Nothing to install.
get_schedule 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_schedule 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_schedule. 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_schedule is provided by the Open Assembly MCP server (kyusik-yang/open-assembly-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 →