PerspectPerspectDocs
Go to Admin
View as Markdown

Releases

This reference is auto-generated from the registered MCP tool providers in perspectapiworkers. It reflects the tools exposed by the per-site Perspect MCP server.

Connection

Use the per-site MCP endpoint:

https://perspect.com/mcp/{siteName}

Authenticate with OAuth or an MCP API key using Authorization: Bearer sk_mcp_....

Tools

release_deploy

Title: Release Deploy

Release Manager tool: deploy the current app source or approved database intent only after a matching Security Auditor approval. Recomputes the source hash and refuses missing, rejected, expired, or source-mismatched approvals. For app_code_deploy, this queues an async build — the result contains buildPending: true and buildComplete: false when the build is queued but not yet finished. Always call app_build_status with the returned build_id after release_deploy to confirm the actual terminal build outcome before reporting success to the user.

Required permission: app.deploy

Parameters

Parameter Type Required Default Description
deploy_intent_type string Yes — Deploy intent to execute. Allowed: app_code_deploy, database_bind, database_unbind, database_migrate, database_delete.
deploy_intent_details object No — Intent-specific details. For database intents, include database_id. For database_migrate, include migrations_dir when not using the default migrations directory.
deploy_requested boolean Yes — Must be true only when the user explicitly asked to deploy or perform this release action.

Example call

{
  "tool": "release_deploy",
  "arguments": {
    "deploy_intent_type": "app_code_deploy",
    "deploy_requested": true
  }
}

Output schema

{
  "type": "object",
  "additionalProperties": true
}

release_record_security_review

Title: Record Security Review

Record the Security Auditor's approval or rejection for the current workspace source snapshot and deploy intent. Approves only when max_severity is none, info, or low and blocking_findings is empty. Medium, high, or critical findings record a rejected review unless an intentional destructive database operation includes valid user risk_acceptance. Approvals expire after 24 hours.

Required permission: app.read

Parameters

Parameter Type Required Default Description
deploy_intent_type string Yes — Deploy intent under review. Use app_code_deploy for app source deploys or a database_* intent for D1 binding, migration, or delete changes. Allowed: app_code_deploy, database_bind, database_unbind, database_migrate, database_delete.
deploy_intent_details object No — Intent-specific details. For database intents, include database_id from database_list/database_create. For database_migrate, include migrations_dir when not using the default migrations directory.
max_severity string Yes — Highest finding severity from this review. medium/high/critical reject the deploy candidate. Allowed: none, info, low, medium, high, critical.
summary string Yes — Concise security review summary, including what was reviewed and why it is approved or rejected.
blocking_findings array<object> No — Blocking findings. Leave empty for normal approved reviews. Any item here records a rejected review unless a valid destructive database risk_acceptance is supplied.
risk_acceptance object No — For database_migrate or database_delete only: records explicit user acceptance of intentional destructive database risk. Use only when the user asked for the destructive action and confirmed a restorable backup. confirmation must exactly equal: I understand this permanently changes live D1 data and I have a restorable backup.
deploy_requested boolean Yes — Must be true only when the user explicitly asked to deploy or perform this reviewed release action. Code/content creation requests without deploy intent must not call release tools.

Example call

{
  "tool": "release_record_security_review",
  "arguments": {
    "deploy_intent_type": "app_code_deploy",
    "max_severity": "none",
    "summary": "string",
    "deploy_requested": true
  }
}

Output schema

{
  "type": "object",
  "additionalProperties": true
}

release_review_status

Title: Release Review Status

Release Manager tool: check whether the current workspace source snapshot and deploy intent has a valid, unexpired Security Auditor approval.

Required permission: app.read

Parameters

Parameter Type Required Default Description
deploy_intent_type string Yes — Deploy intent to check. Allowed: app_code_deploy, database_bind, database_unbind, database_migrate, database_delete.
deploy_intent_details object No — Intent-specific details. For database intents, include database_id. For database_migrate, include migrations_dir when not using the default migrations directory.
deploy_requested boolean Yes — Must be true only when the user explicitly asked to deploy or perform this release action.

Example call

{
  "tool": "release_review_status",
  "arguments": {
    "deploy_intent_type": "app_code_deploy",
    "deploy_requested": true
  }
}

Output schema

{
  "type": "object",
  "additionalProperties": true
}

This page is generated from the registered MCP tool providers. Do not edit it by hand.