assign_check_to_group · Pingera MCP Server MCP

WHAT IT DOES

What assign_check_to_group does on Pingera MCP Server

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

WHY IT NEEDS A POLICY

Why assign_check_to_group needs a policy

This tool creates or modifies a relationship between a check and a group in the monitoring service, which constitutes a reversible write operation. It has a medium blast radius—misconfiguration could disable monitoring or group checks incorrectly, impacting observability—but is not destructive (no data loss) nor financial. The empty description prevents higher confidence assessment.

From the tool's definition Tool name 'assign_check_to_group' indicates modification of monitoring configuration by associating a check with a group. No destructive action (deletion), but changes existing relationships in the monitoring system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

assign_check_to_group Rate-limited

assign_check_to_group 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": {
    "assign_check_to_group": {
      "limits": [
        {
          "counter": "assign_check_to_group_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 Pingera MCP Server, so you can run agents against it safely.

FAQ

Questions about assign_check_to_group

What does the assign_check_to_group tool do? +

assign_check_to_group. It is categorised as a Write tool in the Pingera MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on assign_check_to_group? +

Register the Pingera MCP Server MCP server in PolicyLayer and add a rule for assign_check_to_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 Pingera MCP Server. Nothing to install.

What risk level is assign_check_to_group? +

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

Can I rate-limit assign_check_to_group? +

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

How do I block assign_check_to_group completely? +

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

What MCP server provides assign_check_to_group? +

assign_check_to_group is provided by the Pingera MCP Server MCP server (pingera/pingera-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.