create_mcp_server
Create an MCP server under an existing integration. Registers the server and returns the new id and slug; use list_mcp_integrations first to find the parent integration, then capabilities or access tools to configure it.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/create-mcp-server.md
What create_mcp_server does on Portkey Admin
AI agents use create_mcp_server to create or update resources in Portkey Admin, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Portkey Admin environment.
Why create_mcp_server is rated Medium
This tool creates and registers a new MCP server resource, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code/commands (Execute), or move money (Financial). However, the severity is high because creating new server integrations could enable unauthorized data access or malicious configurations if an AI agent misuses it without proper authorization checks.
From the tool's definition Tool description states 'Create an MCP server under an existing integration. Registers the server and returns the new id and slug' — the verb 'Create' and 'Registers' indicate data creation/modification.
Attacks that exploit this kind of access
The rule that runs create_mcp_server 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 create_mcp_server, this is the rule to start with:
create_mcp_server stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_mcp_server call is checked against it from then on.
Questions about create_mcp_server
Create an MCP server under an existing integration. Registers the server and returns the new id and slug; use list_mcp_integrations first to find the parent integration, then capabilities or access tools to configure it. It is categorised as a Write tool in the Portkey Admin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for create_mcp_server: 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.
create_mcp_server is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_mcp_server 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 create_mcp_server. 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.
create_mcp_server 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