Enable or disable features for a LaunchNotes project (feedback, roadmap, ideas, RSS, voting, SEO indexing). Args: - project_id (string): The ID of the project to update - feedback_enabled (boolean, optional): Enable/disable feedback collection - roadmap_enabled (boolean, optional): Enable/disable...
AI agents use launchnotes_update_project_features 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 modifies project configuration settings reversibly (features can be toggled on/off), which makes it a Write operation rather than Destructive. The impact is limited to project feature toggles without irreversible data loss or external financial implications. Severity is medium because misconfiguration could affect project visibility and functionality, but all changes can be undone.
From the tool's definition Tool description states it can 'Enable or disable features for a LaunchNotes project' with arguments like 'feedback_enabled', 'roadmap_enabled', 'ideas_enabled', 'rss_feed_enabled', 'voting_enabled', and 'noindex'.
Attacks that exploit this kind of access
Enable or disable features for a LaunchNotes project (feedback, roadmap, ideas, RSS, voting, SEO indexing). Args: - project_id (string): The ID of the project to update - feedback_enabled (boolean, optional): Enable/disable feedback collection - roadmap_enabled (boolean, optional): Enable/disable roadmap feature - ideas_enabled (boolean, optional): Enable/disable ideas/feature requests - rss_feed_enabled (boolean, optional): Enable/disable RSS feed - voting_enabled (boolean, optional): Enable/disable voting on ideas - noindex (boolean, optional): Prevent search engine indexing (true = disabled SEO) At least one feature toggle must be provided. Features not specified will remain unchanged. Returns: Confirmation message with updated feature toggles Use Cases: -. 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_update_project_features: 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_update_project_features 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_update_project_features 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_update_project_features. 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_update_project_features 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 →