integrations_get_endpoints
List every endpoint (operationId, method, path) registered on an HTTP-API integration. Identify it by integration_id or base_url. Use this to review what tools exist before integrations.remove_endpoints or add_endpoints.
This record as markdown: /tools/io-github-saloprj-dialogbrain/integrations-get-endpoints.md
What integrations_get_endpoints does on Dialogbrain
AI agents call integrations_get_endpoints to retrieve information from Dialogbrain without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
base_url | string | — | Or the integration's base URL, e.g. https://api.boomnow.com |
integration_id | integer | — | Integration id (from integrations.list). |
Parameters from the server's own tool schema.
Why integrations_get_endpoints is rated Low
This tool retrieves and enumerates HTTP API endpoints from an integration without creating, modifying, or deleting any data. It is purely informational in nature, supporting discovery before other operations. The blast radius of misuse is minimal—an agent could learn about available endpoints but cannot invoke them or modify the integration through this tool alone.
From the tool's definition Tool description states it "List[s] every endpoint" and is used to "review what tools exist before" making changes. The verb 'List' and the stated purpose of information gathering without modifying state indicates a read-only operation.
Risk signalsAccepts URL/endpoint input (base_url) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs integrations_get_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_get_endpoints, this is the rule to start with:
integrations_get_endpoints is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every integrations_get_endpoints call is checked against it from then on.
Questions about integrations_get_endpoints
List every endpoint (operationId, method, path) registered on an HTTP-API integration. Identify it by integration_id or base_url. Use this to review what tools exist before integrations.remove_endpoints or add_endpoints. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
integrations_get_endpoints accepts 2 parameters: base_url, integration_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for integrations_get_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.
integrations_get_endpoints is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the integrations_get_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.
Set action: deny in the PolicyLayer policy for integrations_get_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.
integrations_get_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.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue