get_self_notification

Get a single self-notification by ID (platform notification v1).

Server Dynatrace SaaS MCP Server mnmozi/dynatrace-mcp-saas
Category Read
Risk class Low
Parameters 00 required

What get_self_notification does on Dynatrace SaaS MCP Server

AI agents call get_self_notification to retrieve information from Dynatrace SaaS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_self_notification needs a policy

This tool retrieves a specific self-notification record by its identifier. The 'Get' verb and absence of any modification, deletion, or execution semantics clearly places it in the Read category. The blast radius is minimal as it only accesses existing notification data without altering system state. Severity is low due to limited scope (single notification) and non-sensitive nature of platform notifications.

From the tool's definition Tool name 'get_self_notification' and description 'Get a single self-notification by ID' indicate a retrieval operation with no modification or side effects.

Questions about get_self_notification

What does the get_self_notification tool do? +

Get a single self-notification by ID (platform notification v1). It is categorised as a Read tool in the Dynatrace SaaS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_self_notification? +

Register the Dynatrace SaaS MCP Server MCP server in PolicyLayer and add a rule for get_self_notification: 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 Dynatrace SaaS MCP Server. Nothing to install.

What risk level is get_self_notification? +

get_self_notification is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_self_notification? +

Yes. Add a rate_limit block to the get_self_notification 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.

How do I block get_self_notification completely? +

Set action: deny in the PolicyLayer policy for get_self_notification. 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.

What MCP server provides get_self_notification? +

get_self_notification is provided by the Dynatrace SaaS MCP Server MCP server (mnmozi/dynatrace-mcp-saas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.