create_prompt_label
Create a prompt label for tagging prompt versions such as production, staging, or experiment. Requires either organisation_id or workspace_id to set scope, returns the new label id, and does not assign it to any versions yet.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/create-prompt-label.md
What create_prompt_label does on Portkey Admin
AI agents use create_prompt_label 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_prompt_label is rated Medium
This tool creates metadata (a label) for organizational purposes without modifying existing prompts, triggering external operations, or deleting data. It is a straightforward resource creation operation with no side effects beyond adding a new cataloging tag. Low severity because label creation has minimal blast radius—mislabeling or creating spurious labels does not affect production systems or data integrity.
From the tool's definition Tool description explicitly states 'Create a prompt label' and 'returns the new label id', indicating it creates a new resource. The operation is reversible (labels can be deleted or modified later).
Attacks that exploit this kind of access
The rule that runs create_prompt_label 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_prompt_label, this is the rule to start with:
create_prompt_label 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_prompt_label call is checked against it from then on.
Questions about create_prompt_label
Create a prompt label for tagging prompt versions such as production, staging, or experiment. Requires either organisation_id or workspace_id to set scope, returns the new label id, and does not assign it to any versions yet. 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_prompt_label: 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_prompt_label 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_prompt_label 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_prompt_label. 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_prompt_label 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