AI agents use save_cli_feedback to create or update resources in Codecks — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Codecks environment.
This tool creates and persists new feedback records in the system. While reversible (feedback can presumably be deleted or modified), it modifies the server state by adding new data. The 'save' action indicates data creation rather than retrieval. Severity is medium because feedback submission has limited blast radius—it doesn't delete data, execute arbitrary code, or trigger financial transactions.
From the tool's definition The tool description states 'Save a CLI feedback item' which is a create/write operation that stores new feedback data.
Attacks that exploit this kind of access
Save a CLI feedback item for the development team. No auth needed. It is categorised as a Write tool in the Codecks MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Codecks MCP server in PolicyLayer and add a rule for save_cli_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 Codecks. Nothing to install.
save_cli_feedback 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 save_cli_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.
Set action: deny in the PolicyLayer policy for save_cli_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.
save_cli_feedback is provided by the Codecks MCP server (rangogamedev/codecks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →