更新文件审计状态
AI agents use update_file_status to create or update resources in Code Analysis MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Code Analysis MCP Server environment.
This tool modifies file status/metadata in a reversible manner without deleting data or executing arbitrary code. It aligns with Write category (create, update, post, upload operations). Severity is medium because status updates could affect code audit workflows and permissions, but the change is typically reversible.
From the tool's definition Tool name 'update_file_status' indicates modifying metadata/state of files. Description '更新文件审计状态' (Chinese: 'update file audit status') confirms this is an update operation that changes file-related data.
Attacks that exploit this kind of access
更新文件审计状态. It is categorised as a Write tool in the Code Analysis MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Code Analysis MCP Server MCP server in PolicyLayer and add a rule for update_file_status: 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 Code Analysis MCP Server. Nothing to install.
update_file_status 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_status 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_status. 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_status is provided by the Code Analysis MCP Server MCP server (zeocax/code-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 →