update_monitor_group · Pipiads MCP: Risk & Policy

WHAT IT DOES

What update_monitor_group does on Pipiads

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

PARAMETERS

Parameter	Type	Required	Description
`name`	string	Yes	New group name
`group_id`	string	Yes	Group ID to update

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why update_monitor_group needs a policy

This tool creates or modifies data (renaming a monitor group) without irreversible consequences. The operation is reversible (a group name can be changed again), so it does not qualify as Destructive. There is no code execution, data retrieval only, or financial impact. It is a straightforward Write action with low blast radius if misused.

From the tool's definition Tool description states 'Update a monitor group name' — a reversible modification operation on existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_monitor_group Rate-limited

update_monitor_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": {
    "update_monitor_group": {
      "limits": [
        {
          "counter": "update_monitor_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 Pipiads, so you can run agents against it safely.

FAQ

Questions about update_monitor_group

What does the update_monitor_group tool do? +

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

What parameters does update_monitor_group accept? +

update_monitor_group accepts 2 parameters: name, group_id. Required: name, group_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_monitor_group? +

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

What risk level is update_monitor_group? +

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

Can I rate-limit update_monitor_group? +

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

Set action: deny in the PolicyLayer policy for update_monitor_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 update_monitor_group? +

update_monitor_group is provided by the Pipiads MCP server (pipiads-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.