get_integration
Fetch one integration by slug, including masked key, workspace access, allowed models, and configuration metadata. Use this before editing provider-specific settings or auditing access.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/get-integration.md
What get_integration does on Portkey Admin
AI agents call get_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_integration is rated Low
The tool performs a read-only retrieval operation. The word 'Fetch' clearly indicates data querying. Although it returns sensitive metadata like masked keys and access permissions, the tool itself does not modify state or create side effects — it is purely informational. The suggestion to use it 'before editing' reinforces that it is a prerequisite lookup, not an action tool.
From the tool's definition Tool description states 'Fetch one integration' and 'Use this before editing' — it retrieves integration data (including masked key, workspace access, allowed models, and configuration metadata) with no indication of modification or deletion.
Attacks that exploit this kind of access
The rule that runs get_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_integration, this is the rule to start with:
get_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_integration call is checked against it from then on.
Questions about get_integration
Fetch one integration by slug, including masked key, workspace access, allowed models, and configuration metadata. Use this before editing provider-specific settings or auditing access. 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_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_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_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_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_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