AI agents call list_project_deadlines to retrieve information from Filevine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves deadline information from a Filevine legal case management system. The verb 'list' is a classic read operation with no side effects. It does not create, modify, delete, execute code, or commit financial obligations. The low severity reflects that unauthorized access to deadline information, while potentially sensitive in a legal context, does not enable destructive or financial harm.
From the tool's definition Tool name 'list_project_deadlines' and description 'List all deadlines for a project' indicate a read-only operation that retrieves deadline data without modifying state.
Attacks that exploit this kind of access
List all deadlines for a project. It is categorised as a Read tool in the Filevine MCP Server, which means it retrieves data without modifying state.
Register the Filevine MCP server in PolicyLayer and add a rule for list_project_deadlines: 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 Filevine. Nothing to install.
list_project_deadlines 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 list_project_deadlines 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 list_project_deadlines. 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.
list_project_deadlines is provided by the Filevine MCP server (rosenadvertising/filevine-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 →