AI agents use reply_to_companion to create or update resources in Yocoolab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yocoolab environment.
This tool creates/modifies data (chat messages in the companion UI) in a reversible manner. It sends text replies to a chat interface, which is a write operation. The blast radius is minimal—the worst outcome is spam or misleading messages in the companion chat, which can be deleted or dismissed. No financial, destructive, or code execution implications.
From the tool's definition Send a reply back to the AI Companion panel in the Chrome extension. The reply will appear as an assistant message in the companion chat UI.
Attacks that exploit this kind of access
Send a reply back to the AI Companion panel in the Chrome extension. The reply will appear as an assistant message in the companion chat UI. Supports Markdown formatting. It is categorised as a Write tool in the Yocoolab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Yocoolab MCP server in PolicyLayer and add a rule for reply_to_companion: 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.
reply_to_companion 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 reply_to_companion 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 reply_to_companion. 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.
reply_to_companion 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 →