update_feedback

Update an existing feedback record by ID. Returns the updated status and feedback IDs, changes only value, weight, and metadata, and leaves the trace linkage immutable; use create_feedback only for a new record.

SERVERPortkey Admin SOURCEcodeswhat/portkey-admin-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/codeswhat-portkey-admin-mcp/update-feedback.md

What update_feedback does on Portkey Admin

AI agents use update_feedback 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 update_feedback is rated Medium

This tool performs reversible modifications to existing feedback records (value, weight, metadata updates). No data is deleted or irreversibly overwritten, no external operations are triggered, and no financial or code execution occurs. It falls squarely into the Write category. The blast radius is low since feedback data modifications in an admin/analytics context have limited impact on system stability or security.

From the tool's definition Tool description states 'Update an existing feedback record by ID' and 'changes only value, weight, and metadata' - these are reversible modifications to data fields.

Questions about update_feedback

What does the update_feedback tool do? +

Update an existing feedback record by ID. Returns the updated status and feedback IDs, changes only value, weight, and metadata, and leaves the trace linkage immutable; use create_feedback only for a new record. 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.

How do I enforce a policy on update_feedback? +

Register the Portkey Admin MCP server in PolicyLayer and add a rule for update_feedback: 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.

What risk level is update_feedback? +

update_feedback is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_feedback? +

Yes. Add a rate_limit block to the update_feedback 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.

How do I block update_feedback completely? +

Set action: deny in the PolicyLayer policy for update_feedback. 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.

What MCP server provides update_feedback? +

update_feedback 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Portkey Admin's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.