Tool risk levels

Every MCP tool in FlowCP is automatically classified into one of three risk levels based on the HTTP method of the underlying API endpoint.

Levels

read

HTTP methods: GET

Safe, non-mutating calls that retrieve data. No data is created, modified, or deleted. Read tools have no special restrictions beyond the default-deny model.

Examples: Fetch a user profile, list records, search data.

write

HTTP methods: POST, PATCH, PUT

Calls that create or modify data. Write tools are disabled by default and must be explicitly enabled. Once enabled, no additional confirmation is required.

Examples: Create a record, update a field, submit a form.

destructive

HTTP methods: DELETE

Calls that permanently remove data. Destructive tools have two extra guards on top of the standard default-deny:

1. Must have Require confirmation turned on to be published

2. The MCP runtime enforces the confirmation requirement on every call

Examples: Delete a record, remove a file, cancel a subscription.

Classification rules

HTTP Method	Risk Level
GET	read
POST	write
PATCH	write
PUT	write
DELETE	destructive

Classification is applied automatically during import and cannot be changed manually. If your API exposes a POST endpoint that internally deletes data, FlowCP classifies it as write because FlowCP cannot inspect what the endpoint does internally.

How risk levels are shown

In the Tools list, each tool row displays a colored badge:

• Blue — read

• Yellow — write

• Red — destructive

The stat card at the top of the Tools page shows a count of destructive tools, so you can quickly assess exposure.