get_plenary_agenda
AI agents call get_plenary_agenda 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.
The 'get_' prefix combined with 'plenary_agenda' (a legislative schedule/document) indicates this retrieves information about assembly plenary sessions. Based on the server's purpose of querying a government API and the consistent naming pattern of read-only information retrieval tools, this is classified as Read.
From the tool's definition Tool name 'get_plenary_agenda' indicates a retrieval operation. The server description states it enables 'querying' of legislative data.
Attacks that exploit this kind of access
get_plenary_agenda. 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_plenary_agenda: 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_plenary_agenda 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_plenary_agenda 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_plenary_agenda. 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_plenary_agenda 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 →