# update_plan

Update an existing subscription plan.

Agent View of the PolicyLayer registry record for `update_plan`. HTML page: https://policylayer.com/tools/com-zype-mcp-server/update-plan

## Facts

- Tool: `update_plan`
- Server: Zype Com (`zype/zype-mcp`) — https://policylayer.com/tools/com-zype-mcp-server.md
- Homepage: https://github.com/zype/zype-mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity verified
- Server auth posture: gated_ambiguous
- Server rate-limited: no
- Parameters: 5 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | no | New plan name |
| `active` | boolean | no | Set active status |
| `amount` | string | no | New price |
| `plan_id` | string | yes | The plan ID to update |
| `description` | string | no | New description |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "update_plan",
    "arguments": {
      "plan_id": "<plan_id>"
    }
  }
}
```

## Why update_plan is rated Medium

This tool creates or modifies data reversibly (plan configuration changes), fitting the Write category. It's not Destructive because plan updates are typically reversible (can be updated again). It's not Financial itself—it configures plans rather than moving money—but severity is high because misconfigured subscription plans could affect payment processing for millions of users and cause financial harm downstream.

From the tool's own definition: "Tool name 'update_plan' and description 'Update an existing subscription plan' indicate modification of plan data. The PicPay context (digital wallet, subscriptions, 60M+ users) shows this modifies financial subscription records that affect real users."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Zype Com:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_plan": {
      "limits": [
        {
          "counter": "update_plan_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Zype Com (295)

- `cancel_subscription` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/cancel-subscription.md
- `delete_ad_tag` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-ad-tag.md
- `delete_ad_timing` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-ad-timing.md
- `delete_category` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-category.md
- `delete_consumer` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-consumer.md
- `delete_content_rule_group` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-content-rule-group.md
- `delete_content_rule_profile` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-content-rule-profile.md
- `delete_live_encoder` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-live-encoder.md
- `delete_live_event` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-live-event.md
- `delete_plan` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-plan.md
- `delete_playlist` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-playlist.md
- `delete_playlist_entitlement` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-playlist-entitlement.md
- `delete_program_guide` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-program-guide.md
- `delete_redemption_code` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-redemption-code.md
- `delete_segment` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-segment.md
- `delete_self_hosted_source` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-self-hosted-source.md
- `delete_subscription` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-subscription.md
- `delete_subtitle` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-subtitle.md
- `delete_subtitle_playlist` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-subtitle-playlist.md
- `delete_transaction` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-transaction.md
- `delete_video` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-video.md
- `delete_video_entitlement` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-video-entitlement.md
- `delete_video_favorite` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-video-favorite.md
- `delete_video_source` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-video-source.md
- `delete_zobject` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-zobject.md
- `delete_zobject_type` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-zobject-type.md
- `playout_delete_ad_timing` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/playout-delete-ad-timing.md
- `playout_delete_all_ad_timings` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/playout-delete-all-ad-timings.md
- `playout_delete_block` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/playout-delete-block.md
- `playout_delete_channel` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/playout-delete-channel.md
- …and 265 more: https://policylayer.com/tools/com-zype-mcp-server.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-zype-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-zype-mcp-server
