AI agents use neptime_subscribe to create or update resources in Neptime — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neptime environment.
Subscribing to a channel creates a new subscription record (a reversible write action). It does not delete data, execute code, or involve financial transactions. The daily limit of 50 suggests potential for misuse (mass subscribing), raising severity to medium, but the action is reversible (can be unsubscribed).
From the tool's definition Subscribe to a channel. Limit: 50 subscriptions per day.
Attacks that exploit this kind of access
Subscribe to a channel. Limit: 50 subscriptions per day. Args: - channel_id: Channel ID to subscribe to (required) Returns: Subscription confirmation. It is categorised as a Write tool in the Neptime MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Neptime MCP server in PolicyLayer and add a rule for neptime_subscribe: 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_subscribe 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 neptime_subscribe 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_subscribe. 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_subscribe 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 →