List all currently registered webhook subscriptions
AI agents call list_subscriptions to retrieve information from Nexus Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and enumerates webhook subscriptions—a read-only operation with no data modification, deletion, or execution of external actions. The blast radius if misused is minimal; an agent could enumerate subscriptions but cannot create, modify, delete, or trigger actions. Low severity is appropriate for information disclosure of subscription metadata.
From the tool's definition Tool name 'list_subscriptions' and description 'List all currently registered webhook subscriptions' indicate a retrieval operation that queries existing subscription data without modification or side effects.
Attacks that exploit this kind of access
List all currently registered webhook subscriptions. It is categorised as a Read tool in the Nexus Memory MCP Server, which means it retrieves data without modifying state.
Register the Nexus Memory MCP server in PolicyLayer and add a rule for list_subscriptions: 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 Nexus Memory. Nothing to install.
list_subscriptions 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 list_subscriptions 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 list_subscriptions. 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.
list_subscriptions is provided by the Nexus Memory MCP server (neboy72/nexus-memory). 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 →