Update data in database table.
AI agents use update_data to create or update resources in Claude File Management Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude File Management Server environment.
The tool updates (modifies) data in a database table, which is a reversible Write operation. It does not delete data (which would be Destructive) nor move money (Financial). Severity is 'high' because uncontrolled database updates by an AI agent could corrupt application state, lose important information, or violate data integrity.
From the tool's definition Tool named 'update_data' with description 'Update data in database table.' operates on a database created by 'create_database' and 'create_table' tools in this server's toolkit, indicating it modifies existing data records.
Attacks that exploit this kind of access
Update data in database table. It is categorised as a Write tool in the Claude File Management Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude File Management Server MCP server in PolicyLayer and add a rule for update_data: 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 Claude File Management Server. Nothing to install.
update_data 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 update_data 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 update_data. 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.
update_data is provided by the Claude File Management Server MCP server (vipin1000/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 →