AI agents call get_channel to retrieve information from Mcp Chzzk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward metadata retrieval operation on a live-streaming platform. It queries and returns public channel information without side effects, matching the Read category. The blast radius of misuse is minimal—an agent could retrieve metadata about any channel, but cannot modify data, execute code, or cause harm. Severity is low because the exposure is limited to publicly available channel information.
From the tool's definition Tool retrieves channel metadata (name, image, description, follower count, openLive flag, verified mark) with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get Chzzk channel metadata: name, image, description, follower count, openLive flag, verified mark. It is categorised as a Read tool in the Mcp Chzzk MCP Server, which means it retrieves data without modifying state.
Register the Mcp Chzzk MCP server in PolicyLayer and add a rule for get_channel: 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 Mcp Chzzk. Nothing to install.
get_channel 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_channel 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_channel. 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_channel is provided by the Mcp Chzzk MCP server (saya6k/mcp-chzzk). 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 →