Get full details of a feedback thread including all messages, UI element context (selector, coordinates, element tag), view state, and the annotated screenshot. The screenshot is returned as an image so you can visually see the feedback location.
AI agents call get_thread_context to retrieve information from Yocoolab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves design feedback thread data, UI element details, and screenshots for inspection. It reads and queries information without any side effects, reversible modifications, code execution, or financial impact. The returned screenshot is for visual inspection only.
From the tool's definition Tool name is 'get_thread_context' and description states it 'Get[s] full details' and 'returns' data including messages, context, view state, and screenshot. No modification, deletion, or execution verbs are present.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get full details of a feedback thread including all messages, UI element context (selector, coordinates, element tag), view state, and the annotated screenshot. The screenshot is returned as an image so you can visually see the feedback location. It is categorised as a Read tool in the Yocoolab MCP Server, which means it retrieves data without modifying state.
Register the Yocoolab MCP server in PolicyLayer and add a rule for get_thread_context: 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 Yocoolab. Nothing to install.
get_thread_context 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_thread_context 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_thread_context. 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_thread_context is provided by the Yocoolab MCP server (yocoolab/mcp-server). 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 →