run_prompt_completion
Execute a prompt against the configured model and return the completion. This makes a billable model call, so use render_prompt first when you want to check the template and validate_completion_metadata when billing fields are uncertain.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/run-prompt-completion.md
What run_prompt_completion does on Portkey Admin
AI agents invoke run_prompt_completion to trigger actions in Portkey Admin. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why run_prompt_completion is rated High
The tool executes a live model call which triggers an external operation with real-world effects. It is explicitly noted as 'billable', meaning it incurs financial cost, but the primary action is execution of an external model API call rather than a direct financial transaction (payment, refund, trade).
From the tool's definition Execute a prompt against the configured model and return the completion. This makes a billable model call
Attacks that exploit this kind of access
The rule that runs run_prompt_completion 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 run_prompt_completion, this is the rule to start with:
run_prompt_completion stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 run_prompt_completion call is checked against it from then on.
Questions about run_prompt_completion
Execute a prompt against the configured model and return the completion. This makes a billable model call, so use render_prompt first when you want to check the template and validate_completion_metadata when billing fields are uncertain. It is categorised as a Execute tool in the Portkey Admin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for run_prompt_completion: 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.
run_prompt_completion is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_prompt_completion 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 run_prompt_completion. 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.
run_prompt_completion 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.
Across the catalogue