해결되지 않은 피드백 목록을 중요도순으로 조회합니다.
AI agents call get_pending_feedbacks to retrieve information from Claude Session Continuity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only retrieval operation on feedback data. It retrieves existing feedback in prioritized order without creating, modifying, deleting, or executing any actions. The minimal blast radius of returning existing feedback records makes this a low-severity Read operation.
From the tool's definition Tool name is 'get_pending_feedbacks' with description indicating it queries and retrieves a list of unresolved feedbacks sorted by priority ('조회합니다' = 'retrieves/queries'). No modification, deletion, or execution occurs.
Attacks that exploit this kind of access
해결되지 않은 피드백 목록을 중요도순으로 조회합니다. It is categorised as a Read tool in the Claude Session Continuity MCP Server, which means it retrieves data without modifying state.
Register the Claude Session Continuity MCP server in PolicyLayer and add a rule for get_pending_feedbacks: 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 Claude Session Continuity. Nothing to install.
get_pending_feedbacks 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_pending_feedbacks 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_pending_feedbacks. 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_pending_feedbacks is provided by the Claude Session Continuity MCP server (leesgit/claude-session-continuity-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 →