# get_plan

Get details of a specific plan

Agent View of the PolicyLayer registry record for `get_plan`. HTML page: https://policylayer.com/tools/instantkom-mcp-server/get-plan

## Facts

- Tool: `get_plan`
- Server: instantKOM MCP Server (`instantkom/mcp-server`) — https://policylayer.com/tools/instantkom-mcp-server.md
- Homepage: https://github.com/instantKOM/mcp-server
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_plan",
    "arguments": {}
  }
}
```

## Why get_plan is rated Low

This tool retrieves plan information without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that queries existing plan data. The blast radius of misuse is minimal—an attacker gaining access could only view plan details, not alter billing, subscriptions, or other resources.

From the tool's own definition: "Tool name 'get_plan' and description 'Get details of a specific plan' indicate a retrieval operation with no modification or side effects."

## Use case

AI agents call get_plan to retrieve information from instantKOM MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches instantKOM MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_plan": {}
  }
}
```

## Other tools on instantKOM MCP Server (244)

- `bulk_delete_custom_fields` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/bulk-delete-custom-fields.md
- `delete_account` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-account.md
- `delete_api_key` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-api-key.md
- `delete_bot` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-bot.md
- `delete_bot_env_var` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-bot-env-var.md
- `delete_bot_env_var_value` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-bot-env-var-value.md
- `delete_bot_filter` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-bot-filter.md
- `delete_broadcast` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-broadcast.md
- `delete_broadcast_media` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-broadcast-media.md
- `delete_chat` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-chat.md
- `delete_contact` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-contact.md
- `delete_contact_custom_field_value` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-contact-custom-field-value.md
- `delete_custom_field` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-custom-field.md
- `delete_export` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-export.md
- `delete_feed` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-feed.md
- `delete_flow` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-flow.md
- `delete_flow_edge` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-flow-edge.md
- `delete_flow_node` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-flow-node.md
- `delete_message` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-message.md
- `delete_message_media` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-message-media.md
- `delete_object_folder` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-object-folder.md
- `delete_poll` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-poll.md
- `delete_poll_option` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-poll-option.md
- `delete_qr_code` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-qr-code.md
- `delete_segmentation` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-segmentation.md
- `delete_short_link` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-short-link.md
- `delete_super_widget` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-super-widget.md
- `delete_tag` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-tag.md
- `delete_team_member_by_id` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-team-member-by-id.md
- `delete_template` — Destructive — https://policylayer.com/tools/instantkom-mcp-server/delete-template.md
- …and 214 more: https://policylayer.com/tools/instantkom-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=instantkom-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/instantkom-mcp-server