Get comments on an article. Args: - article_id: Article ID (required) - limit: Max results 1-100 (default: 20) - offset: Pagination offset (default: 0) - sort: Sort order - newest, oldest, top (default: newest) Returns: Array of comments with user info, text, likes, replies.
AI agents call neptime_get_article_comments 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 only queries and returns existing comment data. It has no parameters that modify state, delete data, or trigger external operations. The arguments (article_id, limit, offset, sort) are all for filtering/pagination of read operations. No financial, destructive, or executable side effects are possible.
From the tool's definition Tool retrieves comments on an article with pagination and sorting options. Description states it 'Get comments' and 'Returns: Array of comments with user info, text, likes, replies' — pure data retrieval with no modification, deletion, or side effects.
Attacks that exploit this kind of access
Get comments on an article. Args: - article_id: Article ID (required) - limit: Max results 1-100 (default: 20) - offset: Pagination offset (default: 0) - sort: Sort order - newest, oldest, top (default: newest) Returns: Array of comments with user info, text, likes, replies. 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_article_comments: 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_article_comments 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_article_comments 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_article_comments. 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_article_comments 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 →