team_manager_record_checkpoint

WHAT IT DOES

What team_manager_record_checkpoint does on Team Manager MCP

AI agents use team_manager_record_checkpoint 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.

WHY IT NEEDS A POLICY

Why team_manager_record_checkpoint needs a policy

This tool creates or modifies records in MongoDB for crash recovery purposes. It is a Write operation (data is stored/created) rather than Read (no query), Execute (no code execution triggered), Destructive (data persists and can be recovered), or Financial (no monetary operations).

From the tool's definition The tool 'Persist an agent checkpoint to MongoDB agent_performance_records' performs a create/write operation: it stores data (checkpoint state) in a database collection.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

team_manager_record_checkpoint Rate-limited

team_manager_record_checkpoint 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_record_checkpoint": {
      "limits": [
        {
          "counter": "team_manager_record_checkpoint_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Team Manager MCP, so you can run agents against it safely.

FAQ

Questions about team_manager_record_checkpoint

What does the team_manager_record_checkpoint tool do? +

Persist an agent checkpoint to MongoDB agent_performance_records for crash recovery. 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_record_checkpoint? +

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

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

Can I rate-limit team_manager_record_checkpoint? +

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

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

team_manager_record_checkpoint 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.

// THE FULL RECORD

team_manager_record_checkpoint is one line of Team Manager's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →