team_manager_reset

Reset the room to a clean state and clear this run

SERVERTeam Manager MCP SOURCE0xadvait/team-manager-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xadvait-team-manager-mcp/team-manager-reset.md

WHAT IT DOES

What team_manager_reset does on Team Manager MCP

AI agents call team_manager_reset to permanently remove resources in Team Manager MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why team_manager_reset is rated Critical

The tool clears/resets run state, which destroys task progress, checkpoints, and shared context managed by MongoDB. While potentially recoverable via backups, the action itself is irreversible at runtime and wipes coordinated team planning data. This fits Destructive (data erasure) more than Execute (which would be triggering a new operation).

From the tool's definition "Reset the room to a clean state and clear this run" — irreversibly removes state data from an active team coordination context.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs team_manager_reset safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Team Manager MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For team_manager_reset, this is the rule to start with:

team_manager_reset Hidden

team_manager_reset is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "team_manager_reset"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Team Manager MCP, apply this rule, and every team_manager_reset call is checked against it from then on.

FAQ

Questions about team_manager_reset

What does the team_manager_reset tool do? +

Reset the room to a clean state and clear this run. It is categorised as a Destructive tool in the Team Manager MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on team_manager_reset? +

Register the Team Manager MCP server in PolicyLayer and add a rule for team_manager_reset: 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 Team Manager MCP. Nothing to install.

What risk level is team_manager_reset? +

team_manager_reset is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit team_manager_reset? +

Yes. Add a rate_limit block to the team_manager_reset 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.

How do I block team_manager_reset completely? +

Set action: deny in the PolicyLayer policy for team_manager_reset. 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.

What MCP server provides team_manager_reset? +

team_manager_reset is provided by the Team Manager MCP server (0xadvait/team-manager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Team Manager, and thousands of servers like it.

This server

All 19 Team Manager tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →