This record as markdown: /tools/io-github-portel-dev-ncp/update-file.md
What update_file does on Ncp
AI agents use update_file to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why update_file is rated Medium
This tool modifies existing data reversibly without deleting it, fitting the Write category. Severity is medium because unintended file updates in a shared storage system like Google Drive could affect multiple users and workflows, but the changes are not permanent/irreversible (files can be recovered or reverted). High confidence because the description clearly states the action is an update to an existing file.
From the tool's definition Tool name: 'update_file'. Description: 'Update an existing file in Google Drive'. The verb 'update' indicates modification of existing data in a persistent storage system (Google Drive).
Attacks that exploit this kind of access
The rule that runs update_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_file, this is the rule to start with:
update_file stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every update_file call is checked against it from then on.
Questions about update_file
Update an existing file in Google Drive. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp MCP server in PolicyLayer and add a rule for update_file: 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 Ncp. Nothing to install.
update_file 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_file 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_file. 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_file is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue