docketbird_follow_case
AI agents use docketbird_follow_case to create or update resources in DocketBird MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DocketBird MCP Server environment.
Based on the tool name, 'follow_case' suggests subscribing to or tracking a court case, which is a reversible write/create action (adding a follow relationship). The server context is about court documents and case management. Without a description, confidence is low, but following a case is most likely a Write operation with medium severity since it modifies user preferences or subscriptions.
From the tool's definition Tool name 'docketbird_follow_case'; description is empty or uninformative.
Attacks that exploit this kind of access
docketbird_follow_case. It is categorised as a Write tool in the DocketBird MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DocketBird MCP Server MCP server in PolicyLayer and add a rule for docketbird_follow_case: 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_follow_case is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the docketbird_follow_case 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_follow_case. 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_follow_case 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 →