integrations_remove_endpoints

SERVERDialogbrain SOURCEhttps://api.dialogbrain.com/mcp

Critical RISK CLASS

Category Destructive

Parameters 40 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-saloprj-dialogbrain/integrations-remove-endpoints.md

WHAT IT DOES

What integrations_remove_endpoints does on Dialogbrain

AI agents call integrations_remove_endpoints to permanently remove resources in Dialogbrain, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`paths`	array	—	Exact spec paths to remove (all methods), e.g. ["/socket.io/"].
`base_url`	string	—	Or the integration's base URL.
`operation_ids`	array	—	operationIds to remove, e.g. ["getSocketIo","getPieScreensMenu"].
`integration_id`	integer	—	Integration id (from integrations.list).

Parameters from the server's own tool schema.

RISK

Why integrations_remove_endpoints is rated Critical

This tool permanently removes endpoint registrations from an integration catalog. The removal causes those tools to 'disappear' from the catalog, which is an irreversible destructive action — re-adding them would require reconfiguration. Misuse could cause an AI agent to accidentally remove legitimate API endpoints, breaking integrations.

From the tool's definition Remove endpoints (tools) from an HTTP-API integration... the removed tools disappear. Returns removed + remaining counts.

Risk signalsAccepts URL/endpoint input (base_url)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs integrations_remove_endpoints safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For integrations_remove_endpoints, this is the rule to start with:

integrations_remove_endpoints Hidden

integrations_remove_endpoints is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "integrations_remove_endpoints"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every integrations_remove_endpoints call is checked against it from then on.

FAQ

Questions about integrations_remove_endpoints

What does the integrations_remove_endpoints tool do? +

Remove endpoints (tools) from an HTTP-API integration — e.g. junk paths like static assets, /socket.io, or SPA routes that aren't real API calls. Identify the integration by integration_id or base_url, and the endpoints to drop by operation_ids (e.g. getSocketIo) and/or paths (e.g. /socket.io/). Re-registers the catalog so the removed tools disappear. Returns removed + remaining counts. It is categorised as a Destructive tool in the Dialogbrain MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does integrations_remove_endpoints accept? +

integrations_remove_endpoints accepts 4 parameters: paths, base_url, operation_ids, integration_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on integrations_remove_endpoints? +

Register the Dialogbrain MCP server in PolicyLayer and add a rule for integrations_remove_endpoints: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Dialogbrain. Nothing to install.

What risk level is integrations_remove_endpoints? +

integrations_remove_endpoints is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit integrations_remove_endpoints? +

Yes. Add a rate_limit block to the integrations_remove_endpoints rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block integrations_remove_endpoints completely? +

Set action: deny in the PolicyLayer policy for integrations_remove_endpoints. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides integrations_remove_endpoints? +

integrations_remove_endpoints is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Dialogbrain, and thousands of servers like it.

This server

All 225 Dialogbrain tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →