AI agents call get_cli_feedback to retrieve information from Codecks without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves previously saved feedback data with optional filtering. It has no side effects, does not execute code, does not modify or delete data, and does not involve financial transactions. The lack of auth requirement actually reduces severity slightly as it suggests the data is not sensitive. This is a straightforward Read operation.
From the tool's definition Tool name contains 'get_' prefix and description states 'Read saved CLI feedback items'. The verb 'Read' and the retrieval-only nature (no modification, deletion, or execution) clearly indicate a data query operation.
Attacks that exploit this kind of access
Read saved CLI feedback items. Optionally filter by category. No auth needed. It is categorised as a Read tool in the Codecks MCP Server, which means it retrieves data without modifying state.
Register the Codecks MCP server in PolicyLayer and add a rule for get_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.
get_cli_feedback 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 get_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 get_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.
get_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 →