get_mcp_integration
Retrieve one MCP integration by id or slug. Returns the full Portkey-side config, including auth type, transport, and masked configuration keys; use get_mcp_integration_metadata for the server
This record as markdown: /tools/codeswhat-portkey-admin-mcp/get-mcp-integration.md
What get_mcp_integration does on Portkey Admin
AI agents call get_mcp_integration 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 get_mcp_integration is rated Low
This tool performs a straightforward data retrieval operation. It returns configuration information about an MCP integration including auth type, transport, and masked keys. There are no indications of data creation, modification, deletion, or execution of external operations. The masking of sensitive keys further suggests this is designed as a safe read operation.
From the tool's definition Tool retrieves an MCP integration configuration by id or slug. The description explicitly states 'Retrieve' and 'Returns', indicating a read-only operation that queries existing data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_mcp_integration 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 get_mcp_integration, this is the rule to start with:
get_mcp_integration 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 get_mcp_integration call is checked against it from then on.
Questions about get_mcp_integration
Retrieve one MCP integration by id or slug. Returns the full Portkey-side config, including auth type, transport, and masked configuration keys; use get_mcp_integration_metadata for the server. 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 get_mcp_integration: 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.
get_mcp_integration 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 get_mcp_integration 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 get_mcp_integration. 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.
get_mcp_integration 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