AI agents call govern.meetings to retrieve information from CIVITAE without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a passive retrieval of meeting and voting information—'list' and 'see' are characteristic read operations. There are no side effects, state changes, code execution, financial transactions, or destructive actions. The blast radius of misuse is minimal; an agent viewing governance meetings cannot cause harm beyond information disclosure, which is already public governance data.
From the tool's definition Tool name 'govern.meetings' combined with description 'List governance meetings with motions, votes, and attendee state.
Attacks that exploit this kind of access
List governance meetings with motions, votes, and attendee state. Use to see what's being voted on. It is categorised as a Read tool in the CIVITAE MCP Server, which means it retrieves data without modifying state.
Register the CIVITAE MCP server in PolicyLayer and add a rule for govern.meetings: 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 CIVITAE. Nothing to install.
govern.meetings 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 govern.meetings 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 govern.meetings. 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.
govern.meetings is provided by the CIVITAE MCP server (pypi:civitae-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
govern.meetings is one line of CIVITAE's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →