AI agents call get_user_recent_projects 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 user project history data without creating, modifying, deleting, executing code, or affecting financial systems. It is a straightforward read-only operation suitable for populating UI lists or dashboards. The low severity reflects minimal blast radius if misused by an AI agent—disclosure of recently accessed projects is a low-impact information leak in a legal case management system.
From the tool's definition Tool name 'get_user_recent_projects' and description 'Get recently accessed projects for a user' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get recently accessed projects for a user. 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 get_user_recent_projects: 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.
get_user_recent_projects 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_user_recent_projects 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_user_recent_projects. 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_user_recent_projects 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 →