# reject_proposal

Reject a pending proposal so it will not be launched. Returns the updated {data: SignalProposal (status

Agent View of the PolicyLayer registry record for `reject_proposal`. HTML page: https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/reject-proposal

## Facts

- Tool: `reject_proposal`
- Server: Max MCP Server (`digital-crew-technologies/max-mcp-server`) — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server.md
- Homepage: https://github.com/Digital-Crew-Technologies/max-mcp-server
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why reject_proposal is rated Medium

This tool modifies the state of a proposal object by changing its status, which is a reversible Write operation. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), nor move money (would be Financial). The change is reversible—a rejected proposal could theoretically be re-approved or reopened.

From the tool's own definition: "Tool name 'reject_proposal' and description 'Reject a pending proposal so it will not be launched. Returns the updated {data: SignalProposal (status' indicates modification of a proposal's status field from pending to rejected."

## Use case

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

## Recommended policy (PolicyLayer)

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

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

## Other tools on Max MCP Server (414)

- `automation_cancel_run` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/automation-cancel-run.md
- `automation_delete` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/automation-delete.md
- `automation_discard_draft` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/automation-discard-draft.md
- `bulk_delete_organizations` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/bulk-delete-organizations.md
- `bulk_delete_prospects` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/bulk-delete-prospects.md
- `cancel_meeting` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/cancel-meeting.md
- `cancel_meeting_series` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/cancel-meeting-series.md
- `cancel_warmup` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/cancel-warmup.md
- `clear_failed_requests` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/clear-failed-requests.md
- `decline_meeting` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/decline-meeting.md
- `delete_calendar_event` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-calendar-event.md
- `delete_campaign` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-campaign.md
- `delete_campaign_attachment` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-campaign-attachment.md
- `delete_deal` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-deal.md
- `delete_deal_attachment` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-deal-attachment.md
- `delete_deal_pipeline` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-deal-pipeline.md
- `delete_deal_stage` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-deal-stage.md
- `delete_deal_stage_rule` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-deal-stage-rule.md
- `delete_icp` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-icp.md
- `delete_meeting_link` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-meeting-link.md
- `delete_organization` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-organization.md
- `delete_prospect` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-prospect.md
- `delete_prospect_list` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-prospect-list.md
- `delete_prospect_profile_hook` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-prospect-profile-hook.md
- `delete_saved_view` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-saved-view.md
- `delete_schedule_preset` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-schedule-preset.md
- `disconnect_data_supplier` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/disconnect-data-supplier.md
- `pipeline_delete_campaign_route` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/pipeline-delete-campaign-route.md
- `pipeline_delete_canvas_draft` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/pipeline-delete-canvas-draft.md
- `pipeline_delete_link` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/pipeline-delete-link.md
- …and 384 more: https://policylayer.com/tools/digital-crew-technologies-max-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=digital-crew-technologies-max-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/digital-crew-technologies-max-mcp-server
