get_retention_events
AI agents call get_retention_events to retrieve information from CourtListener MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the naming convention 'get_*', this tool retrieves data (retention events, likely related to judge retention information) without modifying, executing, or destructing anything. The pattern matches sibling tools like 'get_judge', 'get_docket', 'get_cluster' which are all read operations on the CourtListener legal database.
From the tool's definition Tool name 'get_retention_events' suggests retrieval of retention event data. The verb 'get' indicates a read operation. Description is empty, limiting certainty.
Attacks that exploit this kind of access
get_retention_events. It is categorised as a Read tool in the CourtListener MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CourtListener MCP Server MCP server in PolicyLayer and add a rule for get_retention_events: 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 CourtListener MCP Server. Nothing to install.
get_retention_events 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_retention_events 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_retention_events. 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_retention_events is provided by the CourtListener MCP Server MCP server (upsd1/courtlistener-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 →