제품별 변경 계획 생성
AI agents use generate_change_plan to create or update resources in Sangfor Mcp Workflow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sangfor Mcp Workflow environment.
This tool generates/creates change planning documentation as part of the project workflow. It modifies/creates data (change plans) but does not execute infrastructure changes, delete data irreversibly, or move funds. While related to change management, the tool itself only produces a plan document rather than applying the changes, making it Write category.
From the tool's definition Tool name 'generate_change_plan' and description '제품별 변경 계획 생성' (generate change plan by product) indicate creation of a change plan document.
Attacks that exploit this kind of access
제품별 변경 계획 생성. It is categorised as a Write tool in the Sangfor Mcp Workflow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sangfor Mcp Workflow MCP server in PolicyLayer and add a rule for generate_change_plan: 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 Sangfor Mcp Workflow. Nothing to install.
generate_change_plan 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 generate_change_plan 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 generate_change_plan. 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.
generate_change_plan is provided by the Sangfor Mcp Workflow MCP server (whelp99-code/sangfor-mcp-workflow). 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 →