manage_group
AI agents use manage_group to create or update resources in Windows Operations MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Windows Operations MCP environment.
The tool name 'manage_group' on a Windows system management server most likely manages Windows user groups (create, modify, add/remove members). This is a Write operation at minimum, but could span into Execute or Destructive depending on implementation. Given sibling tools like 'add_user' and 'agentic_system_hardening', this is likely group management (net localgroup or similar).
From the tool's definition Tool name 'manage_group' on a Windows Operations MCP server described as enabling 'comprehensive Windows system management' including user operations (sibling tool 'add_user' visible).
Attacks that exploit this kind of access
manage_group. It is categorised as a Write tool in the Windows Operations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Windows Operations MCP server in PolicyLayer and add a rule for manage_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 Windows Operations MCP. Nothing to install.
manage_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 manage_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 manage_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.
manage_group is provided by the Windows Operations MCP server (sandraschi/windows-operations-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 →