AI agents call get_selection_history 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 is a pure data retrieval operation that queries selection history. There are no side effects, no code execution, no data modification, and no destructive actions. The tool simply provides read-only access to past user selections, making it a straightforward Read category tool.
From the tool's definition Tool returns historical data ('Returns the last N element selections') without modifying, deleting, or executing any operations. It retrieves recent user selections from the Chrome extension.
Attacks that exploit this kind of access
Returns the last N element selections from the Chrome extension, newest first. Useful for comparing multiple elements or reviewing recent selections. 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_selection_history: 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_selection_history 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_selection_history 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_selection_history. 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_selection_history 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 →