docketbird_list_courts
AI agents call docketbird_list_courts to retrieve information from DocketBird MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve a list of available courts from the DocketBird API. Listing courts is a non-destructive query operation with no side effects—it only retrieves metadata about court entities. The blast radius of misuse is minimal: an attacker could enumerate courts but cannot modify data, execute commands, or cause financial harm.
From the tool's definition Tool name 'docketbird_list_courts' and sibling tools (docketbird_list_cases, docketbird_search_documents, docketbird_get_case_details) indicate query/retrieval operations.
Attacks that exploit this kind of access
docketbird_list_courts. It is categorised as a Read tool in the DocketBird MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DocketBird MCP Server MCP server in PolicyLayer and add a rule for docketbird_list_courts: 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 DocketBird MCP Server. Nothing to install.
docketbird_list_courts 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 docketbird_list_courts 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 docketbird_list_courts. 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.
docketbird_list_courts is provided by the DocketBird MCP Server MCP server (justlyai/docketbird-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 →