AI agents call neptime_get_article 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 an article by its ID and returns its data without any side effects. No data is created, modified, deleted, or executed. The operation is a simple query of existing data, fitting the Read category with low severity since unauthorized retrieval of article content poses minimal risk compared to destructive or financial operations.
From the tool's definition Tool description states 'Get a specific article by ID' and returns 'Full article object with title, text, author, comments count.' The verb 'get' and the retrieval-only nature with no modification or deletion confirm read-only behavior.
Attacks that exploit this kind of access
Get a specific article by ID. Args: - article_id: Article ID (required) Returns: Full article object with title, text, author, comments count. 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: 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 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 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. 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 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 →