This record as markdown: /tools/com-files-python-mcp/update-group.md
What Update_Group does on Files Com
AI agents use Update_Group 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_Group is rated Medium
This tool modifies group configuration or metadata within Files.com. As an update operation, it creates reversible changes to existing resources. The severity is medium because unauthorized group modifications could affect access controls and user permissions, but the changes are not destructive (can be reverted) and do not directly move money or execute arbitrary code.
From the tool's definition Tool name is 'Update_Group' and description states 'Update Group'. Update operations modify existing data reversibly.
Attacks that exploit this kind of access
The rule that runs Update_Group 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_Group, this is the rule to start with:
Update_Group 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_Group call is checked against it from then on.
Questions about Update_Group
Update_Group 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_Group: 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_Group 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_Group 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_Group. 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_Group 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