validate_completion_metadata
Preflight billing metadata before run_prompt_completion. Validates required fields and values without making changes, so you can catch attribution errors before paying for the call.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/validate-completion-metadata.md
What validate_completion_metadata does on Portkey Admin
AI agents call validate_completion_metadata 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 validate_completion_metadata is rated Low
The tool performs validation and inspection of completion metadata before execution. It explicitly does not make changes, create records, or trigger billing. It is a data inspection/query operation with no reversible or irreversible modifications, making it Read category. Severity is low because misuse cannot cause harm — it only checks data validity.
From the tool's definition Tool description states it 'Validates required fields and values without making changes' — this is a read-only preflight check with no side effects.
Attacks that exploit this kind of access
The rule that runs validate_completion_metadata 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 validate_completion_metadata, this is the rule to start with:
validate_completion_metadata 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 validate_completion_metadata call is checked against it from then on.
Questions about validate_completion_metadata
Preflight billing metadata before run_prompt_completion. Validates required fields and values without making changes, so you can catch attribution errors before paying for the call. 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 validate_completion_metadata: 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.
validate_completion_metadata 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 validate_completion_metadata 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 validate_completion_metadata. 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.
validate_completion_metadata 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