create_idea
Drops a new idea into the Boardroom Ideas board so the pack can react and vote. Use when something is too speculative for a todo but worth capturing. agent_id required. Posts an 'idea-created' Boardroom event.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/create-idea.md
What create_idea does on UnClick
AI agents use create_idea to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | Yes | Short title (max 200 chars) |
agent_id | string | Yes | |
description | string | — | Optional longer description (max 4000 chars) |
Parameters from the server's own tool schema.
Why create_idea is rated Medium
This tool creates a new idea record in a collaborative board system. The action is reversible (ideas can be deleted or modified), has limited blast radius (only creates data in an internal ideas board), and does not modify existing data, trigger external operations, delete data, or move money. It falls clearly into the Write category with low severity due to the benign nature of idea curation.
From the tool's definition Tool description explicitly states it 'Drops a new idea into the Boardroom Ideas board' and 'Posts an idea-created Boardroom event', indicating creation of new data that can be modified or removed later.
Attacks that exploit this kind of access
The rule that runs create_idea safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_idea, this is the rule to start with:
create_idea stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every create_idea call is checked against it from then on.
Questions about create_idea
Drops a new idea into the Boardroom Ideas board so the pack can react and vote. Use when something is too speculative for a todo but worth capturing. agent_id required. Posts an 'idea-created' Boardroom event. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_idea accepts 3 parameters: title, agent_id, description. Required: title, agent_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for create_idea: 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 UnClick. Nothing to install.
create_idea 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 create_idea 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 create_idea. 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.
create_idea is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue