Schedule an announcement to be published automatically at a specific future date and time. Args: - announcement_id (string): The ID of the announcement to schedule - scheduled_at (string): When to publish (ISO 8601 format, must be in future) - scheduled_at_timezone (string, optional): Timezone (e...
AI agents use launchnotes_schedule_announcement to create or update resources in LaunchNotes MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LaunchNotes MCP Server environment.
This tool creates or modifies a scheduling configuration for an announcement, which is a Write operation—it changes data state reversibly (the scheduled publication time can be updated or cancelled). While publishing announcements could have business impact, the act of scheduling itself is not Destructive (no data is deleted), not Execute (no arbitrary code/commands run), and not Financial.
From the tool's definition The tool description states it will "Schedule an announcement to be published automatically at a specific future date and time," which is a reversible modification operation.
Attacks that exploit this kind of access
Schedule an announcement to be published automatically at a specific future date and time. Args: - announcement_id (string): The ID of the announcement to schedule - scheduled_at (string): When to publish (ISO 8601 format, must be in future) - scheduled_at_timezone (string, optional): Timezone (e.g.,. It is categorised as a Write tool in the LaunchNotes MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LaunchNotes MCP Server MCP server in PolicyLayer and add a rule for launchnotes_schedule_announcement: 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 LaunchNotes MCP Server. Nothing to install.
launchnotes_schedule_announcement 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 launchnotes_schedule_announcement 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 launchnotes_schedule_announcement. 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.
launchnotes_schedule_announcement is provided by the LaunchNotes MCP Server MCP server (launchnotes/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 →