team_manager_kill_agent

Record that the MCP host killed or lost an agent after checkpoint persistence. This updates MongoDB state; it does not kill an OS process.

SERVERTeam Manager MCP SOURCE0xadvait/team-manager-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What team_manager_kill_agent does on Team Manager MCP

AI agents use team_manager_kill_agent to create or update resources in Team Manager MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Team Manager MCP environment.

RISK

Why team_manager_kill_agent is rated Medium

The tool's primary function is to update shared MongoDB context to reflect an agent's termination status. This is a write operation—it modifies data reversibly and allows recovery/reactivation tracking via the checkpoint system.

From the tool's definition Tool description states 'This updates MongoDB state' indicating a reversible modification of data. The tool records agent termination events in a coordination system but does not irreversibly delete records (Destructive) or execute external commands (Execute).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs team_manager_kill_agent 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_kill_agent, this is the rule to start with:

team_manager_kill_agent Rate-limited

team_manager_kill_agent stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "team_manager_kill_agent": {
      "limits": [
        {
          "counter": "team_manager_kill_agent_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_kill_agent call is checked against it from then on.

FAQ

Questions about team_manager_kill_agent

What does the team_manager_kill_agent tool do? +

Record that the MCP host killed or lost an agent after checkpoint persistence. This updates MongoDB state; it does not kill an OS process. It is categorised as a Write tool in the Team Manager MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on team_manager_kill_agent? +

Register the Team Manager MCP server in PolicyLayer and add a rule for team_manager_kill_agent: 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_kill_agent? +

team_manager_kill_agent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit team_manager_kill_agent? +

Yes. Add a rate_limit block to the team_manager_kill_agent 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_kill_agent completely? +

Set action: deny in the PolicyLayer policy for team_manager_kill_agent. 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_kill_agent? +

team_manager_kill_agent 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 →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →