AI agents use pin_note to create or update resources in Filevine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Filevine environment.
Pinning a note is a reversible write operation that modifies the state or organization of data (note visibility/priority) without deleting or executing external code. In the context of Filevine's legal case management, this represents a metadata change. Severity is medium because while reversible, modifying note organization in active legal cases could affect team collaboration and case workflow if misused at scale.
From the tool's definition Tool name 'pin_note' and description 'Pin a note' indicates modification of note metadata/state (pinning status) within a case management system.
Attacks that exploit this kind of access
Pin a note. It is categorised as a Write tool in the Filevine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Filevine MCP server in PolicyLayer and add a rule for pin_note: 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.
pin_note 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 pin_note 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 pin_note. 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.
pin_note 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 →