Call this before any provider-backed tool. It resolves the requested content scope to configured provider integrations and reports labels, purpose, enabled tools, and missing env var names without exposing secret values or raw provider ids.
AI agents call list_integrations to retrieve information from Open MCP Knowledgebase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
list_integrations queries internal state (configured integrations and their metadata) and returns information to the caller. It does not modify any data, trigger external operations, or have destructive effects. This is a straightforward Read operation typical of inventory/listing tools.
From the tool's definition Tool description states it 'resolves...and reports labels, purpose, enabled tools' — pure information retrieval with 'no side effects' (query only). Does not create, modify, delete, execute code, or move money.
Attacks that exploit this kind of access
Call this before any provider-backed tool. It resolves the requested content scope to configured provider integrations and reports labels, purpose, enabled tools, and missing env var names without exposing secret values or raw provider ids. It is categorised as a Read tool in the Open MCP Knowledgebase MCP Server, which means it retrieves data without modifying state.
Register the Open MCP Knowledgebase MCP server in PolicyLayer and add a rule for list_integrations: 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 Open MCP Knowledgebase. Nothing to install.
list_integrations 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 list_integrations 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 list_integrations. 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.
list_integrations is provided by the Open MCP Knowledgebase MCP server (no-product/knowledgebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →