View notification configuration (keywords, webhook, telegram, clipboard).
AI agents call get_notifications_config to retrieve information from Overlord MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves notification settings (keywords, webhook, telegram, clipboard configurations) without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that queries existing configuration state.
From the tool's definition Tool name uses 'get_' verb and description states 'View notification configuration', indicating read-only retrieval of settings without modification or execution.
Attacks that exploit this kind of access
View notification configuration (keywords, webhook, telegram, clipboard). It is categorised as a Read tool in the Overlord MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Overlord MCP Server MCP server in PolicyLayer and add a rule for get_notifications_config: 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 Overlord MCP Server. Nothing to install.
get_notifications_config 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 get_notifications_config 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 get_notifications_config. 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.
get_notifications_config is provided by the Overlord MCP Server MCP server (skeeminator/overlord-mcp). 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 →