List configured third-party integrations (webhooks, data connectors, export targets, etc.).
AI agents call list_integrations to retrieve information from NeuronSearchLab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns information about existing integrations. It performs a read operation with no side effects, no code execution, no data modification, and no irreversible actions. The ability to list integrations could expose integration details, but this is a read-only information retrieval operation that poses minimal risk compared to actually invoking or modifying those integrations.
From the tool's definition Tool name 'list_integrations' and description 'List configured third-party integrations' indicate retrieval of configuration information without modification or execution of external actions.
Attacks that exploit this kind of access
List configured third-party integrations (webhooks, data connectors, export targets, etc.). It is categorised as a Read tool in the NeuronSearchLab MCP Server, which means it retrieves data without modifying state.
Register the NeuronSearchLab 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 NeuronSearchLab. 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 NeuronSearchLab MCP server (neuronsearchlab/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 →