AI agents call neptime_get_channel to retrieve information from Neptime without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries channel data with no side effects. It is a straightforward data retrieval operation that fits the Read category. Severity is low because exposing public channel information poses minimal risk; an AI agent cannot cause harm by repeatedly querying channel metadata.
From the tool's definition Tool description states 'Get channel information by ID' and returns read-only channel metadata (name, avatar, subscriber count, video count, description). No modification, deletion, or execution occurs.
Attacks that exploit this kind of access
Get channel information by ID. Args: - channel_id: Channel ID (required) Returns: Channel object with name, avatar, subscriber count, video count, description. It is categorised as a Read tool in the Neptime MCP Server, which means it retrieves data without modifying state.
Register the Neptime MCP server in PolicyLayer and add a rule for neptime_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 Neptime. Nothing to install.
neptime_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 neptime_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 neptime_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.
neptime_get_channel is provided by the Neptime MCP server (neptime-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 →