Update multiple files analysis in batch (explicit agent-controlled)
AI agents use update_files to create or update resources in SACL MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SACL MCP Server environment.
This tool modifies file analysis data in a batch operation. While the description is somewhat vague about whether it modifies actual file contents or only analysis metadata, the core action is a write operation that creates or modifies data. The 'explicit agent-controlled' qualifier suggests the agent directly invokes this, raising the risk if misused.
From the tool's definition Tool name is 'update_files' with description stating it will 'Update multiple files analysis in batch'. The verb 'update' and the explicit mention of batch file modification indicates the tool creates or modifies data.
Attacks that exploit this kind of access
Update multiple files analysis in batch (explicit agent-controlled). It is categorised as a Write tool in the SACL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SACL MCP Server MCP server in PolicyLayer and add a rule for update_files: 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 SACL MCP Server. Nothing to install.
update_files 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_files 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_files. 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_files is provided by the SACL MCP Server MCP server (ulasbilgen/sacl). 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 →