This record as markdown: /tools/com-files-python-mcp/update-user.md
What Update_User does on Files Com
AI agents use Update_User to create or update resources in Files Com, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Files Com environment.
Why Update_User is rated Medium
This tool creates or modifies user account data reversibly. While user modifications can have significant consequences (permission changes, access control), they are not irreversible deletions (which would be Destructive) and do not involve financial transactions.
From the tool's definition Tool name is 'Update_User' with description 'Update User'. It modifies user data in a Files.com environment.
Attacks that exploit this kind of access
The rule that runs Update_User safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Files Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For Update_User, this is the rule to start with:
Update_User 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 Files Com, apply this rule, and every Update_User call is checked against it from then on.
Questions about Update_User
Update_User is a write tool on the Files Com MCP server. It is categorised as a Write tool in the Files Com MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Files Com MCP server in PolicyLayer and add a rule for Update_User: 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 Files Com. Nothing to install.
Update_User 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_User 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_User. 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_User is provided by the Files Com MCP server (files-com-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Files Com, and thousands of servers like it.
This server
Across the catalogue