list_mcp_integrations
List MCP integrations in the organization. Returns paginated integration records plus total and has_more for discovering integration IDs; use get_mcp_integration for one integration
This record as markdown: /tools/codeswhat-portkey-admin-mcp/list-mcp-integrations.md
What list_mcp_integrations does on Portkey Admin
AI agents call list_mcp_integrations to retrieve information from Portkey Admin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_mcp_integrations is rated Low
This tool queries and returns existing MCP integration records in a paginated format. It performs no writes, deletes, executions, or financial operations. The action is read-only with no side effects, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'list_mcp_integrations' and description 'List MCP integrations in the organization. Returns paginated integration records plus total and has_more' indicate a pure retrieval operation that returns data without modifying it.
Attacks that exploit this kind of access
The rule that runs list_mcp_integrations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Portkey Admin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_mcp_integrations, this is the rule to start with:
list_mcp_integrations 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 Portkey Admin, apply this rule, and every list_mcp_integrations call is checked against it from then on.
Questions about list_mcp_integrations
List MCP integrations in the organization. Returns paginated integration records plus total and has_more for discovering integration IDs; use get_mcp_integration for one integration. It is categorised as a Read tool in the Portkey Admin MCP Server, which means it retrieves data without modifying state.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for list_mcp_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 Portkey Admin. Nothing to install.
list_mcp_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_mcp_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_mcp_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_mcp_integrations is provided by the Portkey Admin MCP server (codeswhat/portkey-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Portkey Admin, and thousands of servers like it.
This server
Across the catalogue