List notifications from the Plugged.in system with optional filters for unread only and result limit
AI agents call pluggedin_list_notifications to retrieve information from Pluggedin Mcp Proxy 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 notification data from the system without creating, modifying, deleting, or executing any operations. It is purely informational in nature with minimal blast radius if misused by an AI agent—worst case being exposure of notification content that may already be accessible to the authenticated user.
From the tool's definition Tool name 'list_notifications' and description 'List notifications from the Plugged.in system with optional filters' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access pluggedin_list_notifications gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pluggedin Mcp Proxy, and nothing reaches the server without passing your rules. This is the rule we recommend for pluggedin_list_notifications:
{
"version": "1",
"default": "deny",
"tools": {
"pluggedin_list_notifications": {}
}
}pluggedin_list_notifications is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List notifications from the Plugged.in system with optional filters for unread only and result limit. It is categorised as a Read tool in the Pluggedin Mcp Proxy MCP Server, which means it retrieves data without modifying state.
Register the Pluggedin Mcp Proxy MCP server in PolicyLayer and add a rule for pluggedin_list_notifications: 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 Pluggedin Mcp Proxy. Nothing to install.
pluggedin_list_notifications 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 pluggedin_list_notifications 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 pluggedin_list_notifications. 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.
pluggedin_list_notifications is provided by the Pluggedin Mcp Proxy MCP server (veriteknik/pluggedin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 27 Pluggedin Mcp Proxy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
27 Pluggedin Mcp Proxy tools catalogued and risk-classified — across an index of 42,500+ MCP servers.